- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Sat, 5 Jan 2013 15:51:48 -0800
- To: Simon Sapin <simon.sapin@kozea.fr>, W3C Style <www-style@w3.org>
Received on Saturday, 5 January 2013 23:52:16 UTC
Blah, accidentally skipped the list with this. On Jan 4, 2013 10:41 PM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote: > On Fri, Jan 4, 2013 at 8:42 AM, Simon Sapin <simon.sapin@kozea.fr> wrote: > > Le 04/01/2013 17:33, Tab Atkins Jr. a écrit : > >> Have you tested unicode-range? I'm interested in seeing if the u, the +, > >> the -, or the ? can be escaped. I'll test in a few minutes if you > haven't. > > > > No I haven’t. I included it in the patch because it looked easy and > nicely > > consistent, but it can easily be split out. > > > > I have no idea if implementations allow escaping of -+? but I somewhat > feel > > they they shouldn’t. We don’t do that for @ in at-rules or ( in > functions, > > after all. > > It looks like only WebKit and Firefox honor unicode-range at all. > Both of them treat an escaped U in the token as an error. So, I'm > leaving that as it is, only accepting a literal u or U. > > I've made the changes to the url token, though. > > ~TJ >
Received on Saturday, 5 January 2013 23:52:16 UTC