[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

--- Comment #10 from Mike Kamermans <pomax@nihongoresources.com> ---
I'm not sure that would be a good idea. People are going to have to write and
read these structures a lot, making pseudo elements start with a dash will not
be pleasant. Given the established nature of CSS pseudo-selectors, would it
make sense to go with dash-in-name anyway, and either leave the collision up to
the client (with an application warning that an established pseudo-class is
being redeclared, much like how an unknown CSS propertie will throw warnings in
all modern browsers). This will even allow a graceful degradation where new
pseudo-selectors are added to CSS, and sites that don't use them, but were
already using their own now-name-colliding custom pseudo-elements now get a
warning from the browser. The behaviour will be the same as before (the
pseudo-element wins), but the site will do the same as it always did, and the
maintainers can decide to either move with the times, or ignore the problem
without loss of function =)

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

Received on Thursday, 9 May 2013 01:49:35 UTC