160334 - EVENT_STATE_CHANGE with STATE_BUSY flag cleared is fired too early for new page loads

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect)

Description

[Aaron Leventhal]

We are notifying assistive technology that a page is finished loaded when it is
first displayed, instead of when the text of the page is completely loaded.

We should wait to fire the event until the page is completely loaded, otherwise
assistive tech has difficulty loading the page contents into its own buffer.

Comment 1

[Aaron Leventhal]

Waiting to find out from Bill Smith if we're firing this event at the right time
now, in a test build I gave him.

Comment 2

[Aaron Leventhal]

Attachment: Fires final MSAA EVENT_STATE_CHANGE event onwebprogresslistener's STATE_STOP, instead of new window creation

Comment 3

[Aaron Leventhal]

Attachment: Same solution, better patch

Comment 4

[Aaron Leventhal]

Attachment: Deterministic solution - just use progress listener's STATE_STOP to tell us when page is finished. Doesn't appear that window is ever hidden when this happens.

Comment 5

[John Gaunt (redfive)]

Comment on attachment 93778 [details] [diff] [review]
Deterministic solution - just use progress listener's STATE_STOP to tell us when page is finished. Doesn't appear that window is ever hidden when this happens.

r=jgaunt

Comment 6

[Brian Ryner (not reading)]

Comment on attachment 93778 [details] [diff] [review]
Deterministic solution - just use progress listener's STATE_STOP to tell us when page is finished. Doesn't appear that window is ever hidden when this happens.

I'd make sure that this works ok in places where there are multiple documents
in the page (framesets, iframes).  Assuming that all works fine, sr=bryner.

Comment 7

[Aaron Leventhal]

cbecked in a long time ago.