Closed Bug 430053 Opened 16 years ago Closed 14 years ago

XMLHttpRequest + chrome:// url = error

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: telega, Unassigned)

Details

(Whiteboard: [CLOSEME 2010-09-15])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

Using XMLHttpRequest to load html from chrome:// url causes an error to be printed in console. This happes only if: 1) Firefox version is 3.x 2) url is chrome:// 3) Retrieved data is non-XML (no error for XML)

See "Additional Information" for code sample.

Reproducible: Always

Steps to Reproduce:
1. Put index.html & test.html files (listed in "Additional Information") into file system, where they're accessible using chrome:// url.
2. Open index.html file in browser using chrome:// url.
3. See "element not found" error printed in console.
Actual Results:  
Error is printed in console

Expected Results:  
No error

index.html file:
----------------
<script>
  var request = new XMLHttpRequest();
  request.open("GET", "test.html", true);
  request.send("");
</script>
-----------------
test.html file:
-----------------
<br>
-----------------
Reporter, are you still seeing this issue with Firefox 3.6.x or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-09-15]
Version: unspecified → 3.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.