@@ -1166,19 +1166,20 @@ The ''<color>/currentcolor'' keyword</h3>
11661166
11671167 Note: Multi-word keywords in CSS usually separate their component words with hyphens.
11681168 ''<color>/currentcolor'' doesn't, because (deep breath)
1169- it was originally introduced in SVG
1170- as a property value, "current-color" with the usual CSS spelling.
1171- It (along with all other properties and their values)
1172- then became presentation attributes and attribute values,
1173- as well as properties,
1174- to make generation with XSLT easier.
1175- Then all of the presentation attributes were changed
1176- from hyphenated to camelCase, because the DOM
1177- had an isse with hyphen meaning "minus".
1178- But then, they didn't follow CSS conventions
1179- anymore so all the properties and property values
1180- that were <em> already</em> part of CSS were changed back to hyphenated!
1181- ''<color>/currentcolor'' was not a part of CSS at that time, so remained camelCased.
1169+ it was originally introduced in SVG
1170+ as a property value, "current-color" with the usual CSS spelling.
1171+ It (along with all other properties and their values)
1172+ then became presentation attributes and attribute values,
1173+ as well as properties,
1174+ to make generation with XSLT easier.
1175+ Then all of the presentation attributes were changed
1176+ from hyphenated to camelCase, because the DOM
1177+ had an isse with hyphen meaning "minus".
1178+ But then, they didn't follow CSS conventions
1179+ anymore so all the properties and property values
1180+ that were <em> already</em> part of CSS were changed back to hyphenated!
1181+ ''<color>/currentcolor'' was not a part of CSS at that time,
1182+ so remained camelCased.
11821183 Only later did CSS pick it up,
11831184 at which point the capitalization stopped mattering,
11841185 as CSS keywords are <a href="https://infra.spec.whatwg.org/#ascii-case-insensitive">ASCII case-insensitive</a> .
0 commit comments