419626 - Wrong dom node sometimes used to fire start doc load events

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Aaron Leventhal]

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.

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

Mass un-assigning bugs assigned to Aaron.

Comment 2

[alexander :surkov (:asurkov)]

fixed by bug 566103

Comment 3

[alexander :surkov (:asurkov)]

(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.