Permission denied to get property Element.tagName




11 years ago
8 years ago


(Reporter: manos, Assigned: dveditz)


Firefox Tracking Flags

(Not tracked)




(3 attachments)



11 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b4) Gecko/2008030317 Firefox/3.0b4

For some reason, a Sarissa testcase that does:
// ...
} else if(oDoc.documentElement.tagName == "parsererror"){
// ...

Results to an exception: "Permission denied to get property Element.tagName"

Reproducible: Always

Steps to Reproduce:
1. Browse to the given URL
2. Press "Run Testcases"
3. Note the message: "SarissaTestCase.testGetParseErrorTextError, exception Permission denied to get property Element.tagName"
Assignee: nobody → dveditz
Component: General → Security
Product: Firefox → Core
QA Contact: general → toolkit

Comment 1

11 years ago
I've got the same error message trying to do something like this in JavaScript:

galleries = pXML.getElementsByTagName('gallery');

for (var i=0;i<galleries.length;;i++) {
        if (galleries[i].nodeType != 1) continue;

and in this place I've got error 
"Permission denied to get property Element.tagName"

In FF 2.x all works properly.

Reproducible: Always

Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0

Comment 2

11 years ago
Created attachment 323668 [details]
file with a test case

Comment 3

11 years ago
Also seen on Windows XP SP 3

Comment 4

11 years ago
Is there planned any releases or patch in order to remove this bug?

Comment 5

11 years ago
Note that is is probably a duplicate of bug 440422.
(In reply to comment #4)
> Is there planned any releases or patch in order to remove this bug?

A patch would appear in this bug but that usually only happens if this bug gets confirmed as valif bug but the bug is still marked unconfirmed.


11 years ago
Depends on: 434522

Comment 7

11 years ago
I cannot reproduce the issue - neither with nor with the attached testcase. Testing in Firefox 3.0.1 and Gecko/2008080303 Minefield/3.1a2pre.

Comment 8

11 years ago
I can still reproduce with a slightly older build (latest release?).

Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv: Gecko/2008070206 Firefox/3.0.1

Comment 9

11 years ago
It could be related to Firebug plugin.

Comment 10

11 years ago
Probably a duplicate of Bug 440275 or Bug 434522, etc there are a lot of them. Bet its fixed in 3.0.2.

Comment 11

10 years ago
Created attachment 350948 [details]
Demo of bug, complete with screenshots and description.  Enough to confirm bug.

Submittal consists of a directory tree w/ HTML source plus notes and screenshots.  Zipped (loosely) so that WindBlows Extraction Buzzard can handle it.

The bug shows up under  file://  protocol on local computer, but not  http://  from a web-site.

There's an oddity in the Error Console Message that I mention in the Notes; I suspect it might be worth following-up.

Please examine this submittal and confirm the bug...

Comment 12

10 years ago
Created attachment 351354 [details]
Supplement to test case:  Shows error when in a parent dir as well.

This attachment updates the MainDir/index.html and the four iframe.html files to demo the problem in an additional case, i.e., when the iframe-source file is in the parent-dir of the principal file.  Also, it corrects a slight (but irrelevant) flaw, thus verifying that the bug was not caused by that.

Again, the bug only appears when the  MainDir/index.html  file is loaded from the local filesystem...

Comment 13

10 years ago
I am not so sure now if the bug I described here is related to the bug originally filed under this Report, or if it is more appropriately related to Bug 442015.  Please look there for follow-up.
Resolving unconfirmed bugs older than a year with no activity as INCOMPLETE.  Please reopen or file a new bug if you can still reproduce the bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.