- From: <bugzilla@jessica.w3.org>
- Date: Tue, 05 Jun 2012 09:53:54 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17298 --- Comment #6 from Aryeh Gregor <ayg@aryeh.name> 2012-06-05 09:53:53 UTC --- (In reply to comment #5) > Can someone remind me why we reserve ID with space in it at first place? Because some things expect a space-separated list of id's, and id's with spaces in them would break. For instance: <td headers="">, <output for="">, itemref="". > If helping authors is a goal here, I would instead suggest we require > conformance chekcker issue an warning when @id or @class don't match IDENT in > CSS as it's common error that authors think selecting an @id like "1st" or > "2nd" would work in CSS. I think it would be better to fix CSS to accept such id's, since as far as I know they aren't actually ambiguous. Particularly since CSS escape syntax doesn't allow an easy way to escape numbers -- \1 is interpreted as U+0001, IIRC. Of course, authors would still have to escape punctuation like # or . that has special meaning in CSS, but that's more expected, and you can just prefix with a backslash. -- Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Tuesday, 5 June 2012 09:55:56 UTC