- From: <bugzilla@jessica.w3.org>
- Date: Thu, 09 May 2013 17:24:19 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20600 --- Comment #11 from Tab Atkins Jr. <jackalmage@gmail.com> --- (In reply to comment #10) > 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 =) We prefer to avoid these kinds of "graceful" name collisions anyway, because it interferes with people trying to use the "real" versions as we add them in the future. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 9 May 2013 17:24:21 UTC