Closed Bug 523948 Opened 15 years ago Closed 15 years ago

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

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: bzbarsky, Assigned: bzbarsky)

Details

That's what the spec says.
I'm confused and just misread the code.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.