Using MSAA Inspect, look at an untraversed link on a page.
Then activate the link and go back (Alt+Left arrow).
Now looking at the link, notice that it does not report STATE_TRAVERSED.
If you refresh the page with Ctrl+R it will now expose STATE_TRAVERSED.
We're caching that state but we need to fetch it each time the state is requested.
Created attachment 199563 [details] [diff] [review]
Not exposing STATE_TRAVERSED after going back in history
Tree is OPEN:
* checkins to this branch require approval from email@example.com.
* to request drivers' approval, set the attachment flag to approval1.8rc1?.
** include a comment about the value, the risk, and any existing testing.
** land changes and get them verified on the trunk before requesting branch
(In reply to comment #2)
> ** include a comment about the value, the risk, and any existing testing.
Risk is low -- limited to accessibility core which is usually not loaded. Patch
is on trunk.
Value is to provide screen reader users with correct indication of visited state
for links at all times.
Testing was done by myself, but I can have screen reader vendors provide further
testing if needed.
Verified by Doug Geoffray from GW Micro.
Verified that this has been fixed in dev build 10/19/05 build from aaron.