[Webkit-unassigned] [Bug 10436] 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





------- Comment #2 from solutionarchitecture at gmail.com  2006-08-16 13:25 PDT -------
(In reply to comment #1)
> If you need to confirm that the issues indeed were introduced in Safari 2.0.4,
> you could try an earlier version from Multi-Safari at
> http://www.michelf.com/projects/multi-safari/ (be sure to read the "known
> issues" part of that page).
> It would help if you could create a simple test case and attach to this bug
> report, demonstrating what you say in the description, so it can be easily
> verifiable what different browsers do, and what has changed in between
> versions.


Thank you for your response(In reply to comment #1)
> We were able to confirm across other Browsers and that this did work in prior versions.  Thanks for the tip to MultiSafari - this will be very helpful in the future.
> In re: to the test case, attached is a standard HTML page with some very simple client-side code that can be used to test Unicode character handling both in and out of regular expressions in JavaScript.  This page is slightly modified from the original source at http://www.regular-expressions.info/javascriptexample.html - it is simplified (no ads or additional text) and adds some tests that the original page does not.  Tests include:

>>Does a Unicode escape sequence properly get interpreted when written to the screen? 
>>If you compare a Unicode escape sequence to its literal character interpretation, are they equivalent? 
>>Given a regular expression, does a given input match? 

Save the attached file with a .html extension and open it up in the browser to
run the tests.

Given:
Unicode sequence “\u00e9” is the equivalent of “é” 
Unicode sequence “\u0041” is the equivalent of “A” 

I tested in IE 6 on Windows, IE on Mac, and Safari 2.0.4 on Mac.  The IE and
Safari browsers were on the same physical Mac. As you can see from the test
results (in the orginal post), the string functionality in all of the
JavaScript implementations works but the regular expression engines did not
always work.

Attached is a standard HTML page with some very simple client-side code that
can be used to test Unicode character handling both in and out of regular
expressions in JavaScript.  This page is slightly modified from the original
source at http://www.regular-expressions.info/javascriptexample.html - it is
simplified (no ads or additional text) and adds some tests that the original
page does not.  Tests include:

Does a Unicode escape sequence properly get interpreted when written to the
screen? 
If you compare a Unicode escape sequence to its literal character
interpretation, are they equivalent? 
Given a regular expression, does a given input match? 


Save the attached file with a .html extension and open it up in the browser to
run the tests.

Given:
Unicode sequence “\u00e9” is the equivalent of “é” 
Unicode sequence “\u0041” is the equivalent of “A” 


I tested in IE 6 on Windows, IE on Mac, and Safari 2.0.4 on Mac.  The IE and
Safari browsers were on the same physical Mac. As you can see from the test
results, the string functionality in all of the JavaScript implementations
works but the regular expression engines did not always work.

I did not test every single FI regular expression however the ones I did test
further proved the theory.  Anything with a \u sequence didn’t work; very
simple expressions allowing no extended characters worked.

Conclusion - The JavaScript regular expression implementation in this version
of Safari is wrong.  


-- 
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.