_max Sniffing .html (Error: Permission denied to access property 'document Element' at http://mochi .test:8888/tests/suite/browser/test/test) _max Sniffing .html:27
RESOLVED FIXED in seamonkey2.16
> I guess the below mochitest-5 failure stems from this bug. I think > test_maxSniffing needs to be turned into a chrome test (like the FF original) to > fix the permission problem: > > WINNT 5.2 comm-central-trunk debug test mochitests-5/5 on 2012/11/07 10:04:43 > s: sea-win32-04 > 3775 ERROR TEST-UNEXPECTED-FAIL | > /tests/suite/browser/test/test_maxSniffing.html | an unexpected uncaught JS > exception reported through window.onerror - Error: Permission denied to access > property 'documentElement' at > http://mochi.test:8888/tests/suite/browser/test/test_maxSniffing.html:27 > > I don't have a working build right now but will look into this within the next > few days (unless someone reading this gets to it faster). In its own bug of > course, depend on this one and to be pushed to everything up to/including at > least beta. Once it's fixed, mochitest-5 should be green again. :-)
Summary: ERROR TEST-UNEXPECTED-FAIL | /tests/suite/browser/test/test_maxSniffing.html | an unexpected uncaught JS exception reported through window.onerror - Error: Permission denied to access property 'documentElement' → Fix test_maxSniffing.html (Error: Permission denied to access property 'documentElement' at http://mochi.test:8888/tests/suite/browser/test/test_maxSniffing.html:27)
Created attachment 679588 [details] [diff] [review] Patch v1.0 Proposed fix. I had this patch sitting in my tree for about a week but kept forgetting about it.
Comment on attachment 679588 [details] [diff] [review] Patch v1.0 Proposed fix. Verified locally. Please get this fixed on branches, too.
Pushed to comm-central: http://hg.mozilla.org/comm-central/rev/32181af272a3
Target Milestone: --- → seamonkey2.16
Pushed to branches: http://hg.mozilla.org/releases/comm-aurora/rev/2fd086fad5fc http://hg.mozilla.org/releases/comm-beta/rev/daa3c95e0213
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
status-seamonkey2.14: --- → fixed
status-seamonkey2.15: --- → fixed
status-seamonkey2.16: --- → fixed
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.