[Webkit-unassigned] [Bug 21472] escaped characters cause parse errors in idents (for example in @namespace rules)

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=21472


Darin Adler <darin at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |darin at apple.com




--- Comment #7 from Darin Adler <darin at apple.com>  2010-05-06 07:49:21 PST ---
(In reply to comment #5)
> (In reply to comment #4)
> > Created an attachment (id=55223)
 --> (https://bugs.webkit.org/attachment.cgi?id=55223) [details] [details]
> > proposed fix, tested
> 
> Shouldn't the tokenizer lazily unescape escaped characters so that it does not
> potentially complexify/slow down the processing of all stylesheets to handle
> this (very?) rare use case?
> 
> Something like:
> 
> ESCAPED_CHAR    \\(0{0,4}[0-9][0-9](\r\n|[ \t\r\n\f])?) | [a-z])
> {
>     //unput is a flex function to set the next character to be scanned.
>     //unescape is a function to implement (or likely rather reuse from
> somewhere) that returns an unescaped character.
> 
>     /*insert unescaped character */
>     unput(unescape(yytext)); 
> 
>     /*eat up escaped sequence*/
> }

That will probably work better, yes.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.