[Bug 20600] [Shadow]: Custom Pseudo-Elements should follow the same convention as custom element names.

https://www.w3.org/Bugs/Public/show_bug.cgi?id=20600

Mike Kamermans <pomax@nihongoresources.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pomax@nihongoresources.com

--- Comment #8 from Mike Kamermans <pomax@nihongoresources.com> ---
just speaking up as a normal user who will end up having to write CSS
declarations for style hooking, "x-" is just a little nudge forward towards the
mess that CSS has become =)

If a prefix is absolutely necessary, can it be made indicative of what it's
for, like "custom-" or something, so that CSS keeps making sense to people who
have to write/read it?

(I have no idea how to battle the syntax that lands in CSS left and right as
just "a person who has to write CSS"; the style hook syntax involving adding +,
for instance, makes perfect sense to me as a programmer, but as a user I hope
never to have to use it because it just makes CSS less human-unreadable. So
hopefully "x-" isn't kept as prefix, at least)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Wednesday, 27 March 2013 18:17:02 UTC