Visit the URL for TvGuide and try to use the scroll arrows at the top left/top right of the grid, note that the scrolling does not work and this error is shown in the Console/Console2 Error: Security error = NS_ERROR_DOM_SECURITY_ERR Source file: http://www.tvguide.com/Script/s_code.js Line: 614 Security Error: Content at http://googleads.g.doubleclick.net/ may not load data from http://www.tvguide.com/listings/. Warning: Use of captureEvents() is deprecated. To upgrade your code, use the DOM 2 addEventListener() method. For more help http://developer.mozilla.org/en/docs/DOM:element.addEventListener Source file: http://www.tvguide.com/listings/ Using today's trunk, also reported on current Branch builds. I suspect this is a regression or we would have heard about issues before now.

This could be a TVGuide issue perhaps.. has now been reported it was working earlier today, now has quit again... I cannot verify this, other than report in the Build/Branch Forums for today, and yesterday.

Bug 494711? But the reporter marked it WFM...

I do have my UA string modified to show Firefox/3.0.10 in the string, but it seems to make any difference as reported in the bug in comment #2 Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2a1pre) Gecko/20090524 Minefield/3.6a1pre Firefox/3.0.10 (.NET CLR 3.5.30729) ID:20090524042826

Well, now it appears either this bug or: https://bugzilla.mozilla.org/show_bug.cgi?id=494726 Should be duped to the other.... Comments from bug 494726 seem to show that the builds on: The 20090520 build works Nightly builds starting with 20090521 (including the latest 20090524) get this error. Can someone find the changeset range , I still can't figure out how. :(

(In reply to comment #4) > Well, now it appears either this bug or: > > https://bugzilla.mozilla.org/show_bug.cgi?id=494726 > > Should be duped to the other.... > > Comments from bug 494726 seem to show that the builds on: > The 20090520 build works > Nightly builds starting with 20090521 (including the latest 20090524) get this > error. > > Can someone find the changeset range , I still can't figure out how. :( oops! Just realized that regression range is probably for 'Branch', so in theory the regression range for 'Trunk' should be earlier dates.

Checkins for the range given: http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?startdate=2009-05-20&enddate=2009-05-22

We need a tighter window than that - can someone bisect on the hourly builds and get us a narrower range? Also: does switching javascript.options.jit.content to false change the behaviour? There was a TM merge in that range ...

This problem still occurs when JIT.Content is off - so it doesn't look like a TM bug The regression range for 1.9.1 works 2009-05-20 http://hg.mozilla.org/releases/mozilla-1.9.1/rev/acd2d4638228 Broken 2009-05-21 http://hg.mozilla.org/releases/mozilla-1.9.1/rev/f9fdf276d414 Pushlog: http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?fromchange=acd2d4638228&tochange=f9fdf276d414 Will continue to try for a tighter hourly range and a trunk range as well

Based on the DOM error and the pushlog query perhaps bug 473739

On trunk the regression range is: Works 2009-05-20 http://hg.mozilla.org/mozilla-central/rev/0f4de606acd7 Broken 2009-05-21 http://hg.mozilla.org/mozilla-central/rev/d0ae0b099a40 http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=0f4de606acd7&tochange=d0ae0b099a40 Scratch what I said in comment 10 - it looks like the likely bug similar to push pushlogs is bug 455070

CCing Honza - is your bug 455070 to make sessionStorage object conform the WHATWG spec a culprit here?

Can you test the patch in bug 494543?

(In reply to comment #13) > Can you test the patch in bug 494543? Yes, that's the same problem (checked in debugger). I just tested with trunk and patch for that bug, works ok.