[Webkit-unassigned] [Bug 10436] New: Safari May Not Interpret Regular Expression in Compliance with W3C Standard

[bugzilla-daemon at opendarwin.org]

http://bugzilla.opendarwin.org/show_bug.cgi?id=10436

           Summary: Safari May Not Interpret Regular Expression in
                    Compliance with W3C Standard
           Product: WebKit
           Version: 420+ (nightly)
          Platform: Macintosh
        OS/Version: Mac OS X 10.4
            Status: UNCONFIRMED
          Severity: blocker
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at opendarwin.org
        ReportedBy: solutionarchitecture at gmail.com


We are troubleshooting why some websites are no longer working when rendered
with the Safari 2.0.4 browser. The failure begins when client entered data is
validated using regular expressions.  So, we validate that a User's UserID and
Password are 'valid' using the regex - since the regex is failing, a user
cannot enter the site.  This only began with 10.4.7 and 2.0.4 of Safari.  Also
note that it continues to work on 10.4.7 using IE and FireFox.

We have determined no other place to go than to you.

We seem to have localized the issue to Safari's not interpretting regular
expressions consistently. 

For example, we looked at the follwing tests:
> Does the regex \u00e9 match the literal character é? (Validates the regular expression engine understands Unicode escape sequences for extended characters.)? - NO, but it does on IE and FireFox

> Does the regex \u0041 match the literal character A? (Validates the regular expression engine understands Unicode escape sequences for ASCII characters.)? - NO, but it does on IE and FireFox

>Does the regex é match the literal character é? (Validates the regular expression engine understands literal characters outside the ASCII range – this is against ECMAScript spec.)? - Sometimes, but always on IE and FireFox

> Write a Unicode escape sequence to the screen on the client side. (Validates the string parsing and display in the JS engine works.) - Works on all 3

> Is escape sequence \u00e9 equivalent to literal character é? (Validates the string functionality in the JS engine works with extended characters.)? Yes on all 3.

> Is escape sequence \u0041 equivalent to literal character A? (Validates the string functionality in the JS engine works with ASCII characters.)? Yes on all 3

> Does the regex A match the literal character A? (Validates the regular expression engine understands literal characters in the ASCII range – this is ECMAScript spec.)? Yes on all 3

Please help. It's hard for me to believe that the regular expression /
javascript interpreter(s) for Safari aren't working as they have in the past -
but all roads are pointed that way....

Thank you for your review.


-- 
Configure bugmail: http://bugzilla.opendarwin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.