StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Read the <a href="http://www.w3.org/TR/CSS21/syndata.html#characters" rel="noreferrer">W3C spec</a>. (this is CSS 2.1, find the appropriate version for your assumption of browsers)</p> <p>edit: relevant paragraph follows:</p> <blockquote> <p>In CSS, identifiers (including element names, classes, and IDs in selectors) can contain only the characters [a-z0-9] and ISO 10646 characters U+00A1 and higher, plus the hyphen (-) and the underscore (_); they cannot start with a digit, or a hyphen followed by a digit. Identifiers can also contain escaped characters and any ISO 10646 character as a numeric code (see next item). For instance, the identifier "B&W?" may be written as "B\&W\?" or "B\26 W\3F".</p> </blockquote> <p>edit 2: as @mipadi points out in Triptych's answer, there's this <a href="http://www.w3.org/TR/CSS21/syndata.html#vendor-keywords" rel="noreferrer">caveat</a>, also in the same webpage:</p> <blockquote> <p>In CSS, identifiers may begin with '-' (dash) or '_' (underscore). Keywords and property names beginning with '-' or '_' are reserved for vendor-specific extensions. Such vendor-specific extensions should have one of the following formats:</p> <pre><code>'-' + vendor identifier + '-' + meaningful name '_' + vendor identifier + '-' + meaningful name </code></pre> <p>Example(s):</p> <p>For example, if XYZ organization added a property to describe the color of the border on the East side of the display, they might call it -xyz-border-east-color.</p> <p>Other known examples:</p> <pre><code> -moz-box-sizing -moz-border-radius -wap-accesskey </code></pre> <p>An initial dash or underscore is guaranteed never to be used in a property or keyword by any current or future level of CSS. Thus typical CSS implementations may not recognize such properties and may ignore them according to the rules for handling parsing errors. However, because the initial dash or underscore is part of the grammar, CSS 2.1 implementers should always be able to use a CSS-conforming parser, whether or not they support any vendor-specific extensions.</p> <p>Authors should avoid vendor-specific extensions</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload