Closed Bug 52572 Opened 24 years ago Closed 24 years ago

Mozilla DOML2 not in sync with the DOM Level 2 PR.

Categories

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

Product:
Core
Component:
DOM: Core & HTML
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jst, Assigned: jst)

Details

(Whiteboard: [nsbeta3+]) 

Just resently the DOM WG made some last minute changes to the DOM Level 2 spec
that made mozillas DOM interface be different than the ones in the current DOM
Level 2 PR. There changes are trivial and I even have a fix in my tree, ready to
go in.
Nominating for beta3
Status: NEW → ASSIGNED
Keywords: correctness, nsbeta3
Priority: P3 → P1
Marking nsbeta3+.
Whiteboard: [nsbeta3+]
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Reopening, I forgot one change that was made in the DOM Level 2 spec
(CSSValue.valueType is now CSSValue.cssValueType), I have a fix for that already...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Fixed.
Status: REOPENED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Component: DOM Level 2 → DOM HTML
Component: DOM: HTML → DOM: Core & HTML
QA Contact: vidur → general
You need to log in before you can comment on or make changes to this bug.