RML Elements: Difference between revisions

MjnMixael (talk | contribs)
Created page with "{{RML}} When parsing a tag libRocket will look up custom elements associated with the tag name and fall back to a generic element. Very few custom elements are required as mos..."
 
MjnMixael (talk | contribs)
Replaced content with "{{SCPUI moved|https://github.com/MjnMixael/SCPUI/wiki/RML-Elements}}"
Tag: Replaced
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
{{RML}}
{{SCPUI moved|https://github.com/MjnMixael/SCPUI/wiki/RML-Elements}}
When parsing a tag libRocket will look up custom elements associated with the tag name and fall back to a generic element. Very few custom elements are required as most of the power in libRocket comes from styling elements with RCSS to produce the desired layout.
 
The user is encouraged to follow standard HTML guidelines where possible to improve readability across the community. For more information on setting up libRocket to emulate HTML4 see Appendix: HTML4 Style Sheet.
 
==Global Attributes==
Elements have a base set of attributes that are common to across all types, which are:
 
===id===
The unique identifier for the element in this document.
===class===
Assigns a class name or set of class names to an element. Any number of elements may be assigned the same class name or names. Multiple class names must be separated by white space characters. See RCSS.
===style===
Specifies inline style information for the element. See [[Librocket#RCSS|RCSS]].
===on* events===
Event bindings. See [[RML_Events|Events]].

Latest revision as of 18:31, 28 October 2026

This page has moved. SCPUI documentation now lives on the SCPUI GitHub wiki.
See the new version of this page. The old content is still available in this page's history.