The error occurs whilst wiring up a change event in the jQuery page initialization event, and has to do with the selector being used that selects the elements upon which to act. The offending selector is
$('div#Q08AddDialog input:radio[name=Q07Gender], div#Q08AddDialog select[name=Q07CancerType')
It should be noted that this is not a terribly complex selector.
See the attached file for error details from Firebug, including the stack trace, and for the failing source code with context.
Created attachment 553957 [details]
Nicholas: Can you provide the URL to the page?
Looks like a dup of bug 625600.
It's not clear to me in which version that bug is fixed.
(In reply to j.j. from comment #3)
8.0 as it seems.
Bug 625600 won't be fixed until Firefox 8 if I read things right (too bad it has no target milestone set).
Can we do anything with this bug before then?
I did check that I see the problem on Firefox 6 and don't see it on current trunk, so I assume bug 625600 in fact fixed this...
See dups and dependencies of bug 625600.
We let people run into these bugs in Fx7 with eyes open. Should this really happen?
(In reply to j.j. from comment #6)
> tracking-firefox7 ?
> See dups and dependencies of bug 625600.
> We let people run into these bugs in Fx7 with eyes open. Should this really
Sorry about this. We certainly don't want it to happen.
I don't know if we can do anything about it at this point. We could theoretically backport the Yarr refresh to Firefox 7, but that would be the Beta channel--it would be very unusual to backport a patch like that to Beta, and I don't recommend it.
Discussed in triage today - marking tracking-firefox7 and 8.
- is there anything we can safely do in 7? Is cherry picking the yarr fix that touched this at all worthwhile/safe?
- Is it accurate to mark this status-firefox8: fixed?
(In reply to Johnathan Nightingale [:johnath] from comment #8)
> Discussed in triage today - marking tracking-firefox7 and 8.
> - is there anything we can safely do in 7? Is cherry picking the yarr fix
> that touched this at all worthwhile/safe?
That fix was the refresh of Yarr to a later version. It's a pretty big change: that version of Yarr has several bug fixes and optimizations, and wholly replaces PCRE with yarr-interpreter. I also redid the adaptation of Yarr to our code for the refresh.
In terms of risks and benefits, it's about the same as what we have in Fx8/9 now. There are some known bugs in that version of Yarr, which may or may not have been present in the previous version. Compatibility seems to be much better, so far.
> - Is it accurate to mark this status-firefox8: fixed?
What I know is that bug 625600 is landed on mozilla-aurora.
Created attachment 558650 [details]
testcase with jquery 1.6.2
with code from comment 0
Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20100101 Firefox/5.0
I get the "regular expression too complex" message in Fx6 and Fx5 also.
Is this actually a regression from 5.0, as stated in comment 0?
Or just another dup of bug 625600?
No such error message in 8
(In reply to j.j. (mostly inactive in 2013, too) from comment #11)
> I get the "regular expression too complex" message in Fx6 and Fx5 also.
> Is this actually a regression from 5.0, as stated in comment 0?
> Or just another dup of bug 625600?
> No such error message in 8
Mozilla/5.0 (Windows NT 5.1; rv:21.0) Gecko/20100101 Firefox/21.0