Closed Bug 766373 Opened 12 years ago Closed 12 years ago

attributes[0].firstChild is now null in FF14 for a simple DOM request using XMLHttpRequest

Categories

(Core :: DOM: Core & HTML, defect)

14 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: wolverinero79, Unassigned)

References

Details

Attachments

(1 file)

(deleted), application/octet-stream
Details
Attached file DOMTest.zip (deleted) —
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET CLR 1.1.4322; .NET4.0C; .NET4.0E; InfoPath.3; MS-RTC LM 8) Steps to reproduce: See attached files for an example. A simple DOM request via XMLHttpRequest no longer works when checking attributes[0].firstChild of a returned node element. Actual results: Firefox 13 returns an object text string. Firefox 14 returns null. Expected results: Firefox 14 should do what Firefox 13 did (Firefox has done this at least since Firefox 5).
Component: Untriaged → DOM
Product: Firefox → Core
QA Contact: untriaged → general
This was a purposeful change to align with the DOM4 spec, I believe. See bug 737122. Note that use of .firstChild on attribute nodes has warned that it's deprecated since Firefox 7 (see bug 661327, which added the warnings).
Blocks: 737122
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: