JS is doing the right thing in throwing this error. See bug 173067: 'Using "/" character unescaped in RegExp literals causes an error' Also see bug 98306 comment 31, and following comments. Bug 173067 is ready to be marked Invalid, but has been held open due to discrepancies we noticed in our error text. We filed an Evangelism bug on Microsoft for this issue: bug 101070, 'microsoft.com - Using "/" character unescaped in RegExp literals is non-ECMA' That bug was marked fixed, because it seemed like MS had fixed things. But it looks like they haven't gotten all instances of this. Olivier: thank you for this report. I'm going to reassign this to Tech Evangelism for disposition. It is either a dupe of bug 101070, which would then have to be reopened, or it could stand alone -
Assignee: general → english-us
Product: Browser → Tech Evangelism
QA Contact: PhilSchwartau → english-us
Summary: JS RegExp throwing an error → JS throwing an error on unescaped "/" character in RegExp literals
Whiteboard: [ Reopen bug 101070 on the same site? ]
Version: Trunk → unspecified
Conforming summary to TFM item 10 at http://www.mozilla.org/projects/tech-evangelism/site/procedures.html#file-new
Summary: JS throwing an error on unescaped "/" character in RegExp literals → microsoft.com - JS throwing an error on unescaped "/" character in RegExp literals
Fixed in Firefox, see bug 309840.
*** This bug has been marked as a duplicate of 309840 ***
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → DUPLICATE
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.