[Webkit-unassigned] [Bug 50483] REGRESSION: Event calendar fails to load at http://ipfw.edu/calendar/

[bugzilla-daemon at webkit.org]

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





--- Comment #2 from Gavin Barraclough <barraclough at apple.com>  2010-12-05 20:04:55 PST ---
Hi Barton, Alexey,

This will likely have been caused by:
    https://bugs.webkit.org/show_bug.cgi?id=48100
which made our regex syntax checking slightly more stringent, and ECMA-262 compliant.

We should check the regexes in this page, and see whether they comply to the spec – I'm guessing that one is invalid (specifically, contains an invalid range in a character class - one containing a character class escape, e.g. /[d-\d]/)

Assuming that this is the case, I'm not sure not to proceed.

Option A - Hope that this is not a major cause of problems, and that we can continue to move in the direction of greater spec compliance.  I think a good first course of action would be to treat this as an advocacy issue – we should reach out to IPFW, and recommend that they update the problematic source to be ECMA-262 compliant (this will probably just involve adding an extra missing '\' - under ECMA-262 something like /[d-\d]/ contains an invalid range, but you can just escape the hyphen to turn this into a valid regular expression - /[d\-\d]/. This should match our prior behavior).  If IPFW change their code & no more similar issues arise, this could be a good resolution to the problem.

Option B - Retreat from spec compliance on this matter, revert this change, and settle for noncompliant behavior for now (and raise the matter in TC-39 with a view to hopefully improving the future revisions of the spec).

I'd suggest we start by sticking with option A, since reverting the change immediately loses the ability to track whether or not further dupes come in, and this is a broader problem.  I'd like to strongly believe in complying to the spec on this matter, but since the spec disallows a number of further regex features (e.g. octal escapes) that we don't believe we'll be able to remove without breaking the web I don't think 100% compliance is considered a realistic goal here anyway.

cheers,
G.

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