303585 - [fastback] MSAA info missing for new page after going back/forward several times

Status: RESOLVED FIXED

(Core :: Disability Access APIs, defect, P2)

Description

[Dan Kinnunen]

When using the page back and page forward keys to move between previously viewed
web pages, the MSAA program focus does not keep up with the visual page focus in
the browser window. 

To reproduce: 

1. Install and start Inspect Objects (inspect32.exe is part of the Microsoft
Active Accessibility Toolkit, or MozInspect from Aaron Leventhal.)
2. Switch to Deer Park
3. press Ctrl+L to go to location field
4. type “www.cnn.com” and press Enter. Note that Inspect shows MSAA properties
change to reflect the new page.
5. Repeat step 3 (ctrl+L)
6. Repeat step 4 for www.ibm.com
7. Repeat step 3 (ctrl+L)
8. Repeat step 4 for www.yahoo.com
9. Press Alt+BackArrow and Alt+ForwardArrow to move backward and forward through
the ring of web pages.  Watch the Inspect output as the displayed page changes.

Expected result:  The Inspect output should change each time the back/forward
keys are pressed, to reflect information about the currently displayed page.

Actual result: After one or two page changes, the Inspect output no longer
changes.  It becomes “stuck” on one of the pages.  It should change every time
the page is updated, to reflect information on the newly displayed page.  (It
seems to work okay with Firefox version 1.0, and with Internet Explorer).

    - Window-Eyes note:  When the Window-Eyes screen reader is running, it also
cannot keep track of which page is currently displayed in the browser window. 
At one point, the CNN page was showing visually, but Window-Eyes was reading
from the Yahoo page.  It seems likely this is a symptom of the same problem
described above with Inspect.

More information: 
    - Changing the browser.sessionhistory.max_viewers to 0 (zero) seems to mask
the problem (default value is 3).  This can be set by typing "about:config" in
the location field, and finding the parameter in the resulting config option list.

Comment 1

[Aaron Leventhal]

I believe this is caused by bug 298077 -- the docshell isn't focused so we don't
fire a focus event or a statechange event for the page load finish.

Comment 2

[Aaron Leventhal]

(In reply to comment #1)
> I believe this is caused by bug 298077 -- the docshell isn't focused so we don't
> fire a focus event or a statechange event for the page load finish.

This was in fact fixed by the checkin for bug 298077.

Comment 3

[Dan Kinnunen]

I verfied that bug has been resolved in the nightly build of 08/08/05.