Closed Bug 419626 Opened 17 years ago Closed 14 years ago

Wrong dom node sometimes used to fire start doc load events

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: aaronlev, Unassigned)

References

Details

(Keywords: access)

Spun off from bug 417249. Ginn said: "in StartLoadCallback, we don't have the right domNode. At that time, the domNode we get from domWindow is the document being destroyed, not the document being loaded. I think it's still a bug somewhere, and may cause some problems. e.g. state-changed:busy is fired for the wrong target on loading start." I'm not sure if this actually affects any AT usage. AFAICT there is no effect on ATs. If there is a real problem we should raise the priority.
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Depends on: 566103
fixed by bug 566103
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to comment #2) > fixed by bug 566103 It's not an issue any more. We deal with start loading notification for existing documents only because if new document is loading then we get temporary document created because we've asked for a document. There's no still document and therefore it's nothing to deal with.
You need to log in before you can comment on or make changes to this bug.