Closed
Bug 316493
Opened 19 years ago
Closed 17 years ago
JS: uncaught exception: permission denied to get property HTMLDocument.getElementsByTagName
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: trebormojo, Unassigned)
References
()
Details
(Keywords: regression)
Attachments
(1 file)
1.73 KB,
application/octet-stream
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5
I have used Mambo for a long time and now with 1.5 I get JS errors and can't use the editor anymore. I hate to say it, but I have to use IE now for Mambo :(
Reproducible: Always
Steps to Reproduce:
1. must login
2.
3.
Actual Results:
JS Error uncaught exception: permission denied to get property HTMLDocument.getElementsByTagName
Expected Results:
no errors
Something seems to have changed in the javascript permissions or something. I'm just a designer, so don't know much about it only that something has changed since last release.
Comment 1•19 years ago
|
||
Could you create (or make someone else create) a testcase for this issue?
Keywords: regression
Are you using frames?
Does this error happen everytime or only after you re-fresh the page?
I am getting a similar error with the page I am working on.
When I call document.domain I get "null".
Comment 3•17 years ago
|
||
Relatively minimal test case (real-world example minus a few bits of cruft) is at http://tevp.net/banner/banner.htm. Works fine when run from local files, gets the specified error in Firefox 3.0 but I can't reproduce with 2.x
Comment 4•17 years ago
|
||
Sorry, forgot last words...
---------------------------
Gets the specified error only when run from remote system, and only on 3.0 not 2.x.
Comment 5•17 years ago
|
||
Testcase for bug. No bug when run from local machines, and/or on Firefox 2.x. Bug only occurs with 3.x and when sourced from remote systems.
Comment 6•17 years ago
|
||
I get initPage is not defined loading that link... And it seems separate from this bug, which should be resolved/incomplete.
Comment 7•17 years ago
|
||
Tom: Could you create an even smaller testcase and file a separate bug?
Comment 8•17 years ago
|
||
I was trying to create a smaller testcase, but couldn't. Then I remembered that I'm now running Minefield (other FF3 issues making nightlies a better match for me right now) and the bug appears to be resolved. I've even checked the original case that the test case came from and that's fixed as well.
Build id is Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1a1pre) Gecko/2008070802 Minefield/3.1a1pre ID:2008070802
Comment 9•17 years ago
|
||
OK, thanks. If anyone still gets this error, please file a new bug with a testcase.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•