[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


Cedric Vivier <cedricv at neonux.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cedricv at neonux.com




--- Comment #5 from Cedric Vivier <cedricv at neonux.com>  2010-05-06 04:48:48 PST ---
(In reply to comment #4)
> Created an attachment (id=55223)
 --> (https://bugs.webkit.org/attachment.cgi?id=55223) [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*/
}

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