UnsetAttr should fire the mutation event after the removal, not before

RESOLVED INVALID

Status

()

Product:
Core
Component:
DOM
Status:
RESOLVED INVALID
Reported:
10 years ago
Modified:
10 years ago

People

(Reporter: bzbarsky, Assigned: bzbarsky)

Tracking

Version:
Trunk
Platform:
x86
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details
(Assignee)

Description

•
10 years ago 
That's what the spec says.
(Assignee)

Comment 1

•
10 years ago 
I'm confused and just misread the code.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.