Don't fire page loading events when jumping to named anchor

RESOLVED FIXED

Status

()

Core
Disability Access APIs
RESOLVED FIXED
13 years ago
13 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

({access})

Trunk
access
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

13 years ago
When a user jumps to a named anchor link within the same page, the screen reader
should not say "loading page" or anything which indicates that a new page is
loading.

Window-Eyes currently does because it is watching for our "new page is loading"
event.

We shouldn't fire that event when the user is staying on the same page.
(Assignee)

Comment 1

13 years ago
Created attachment 149365 [details] [diff] [review]
Check aWebProgress->GetIsDocumentLoading(). If document is not loading, don't fire doc loading event.
(Assignee)

Updated

13 years ago
Attachment #149365 - Flags: review?(pkw)

Comment 2

13 years ago
Comment on attachment 149365 [details] [diff] [review]
Check aWebProgress->GetIsDocumentLoading(). If document is not loading, don't fire doc loading event.

Looks good to me.
Attachment #149365 - Flags: review?(pkw) → review+
(Assignee)

Updated

13 years ago
Attachment #149365 - Flags: superreview?(darin)

Updated

13 years ago
Attachment #149365 - Flags: superreview?(darin) → superreview+
(Assignee)

Updated

13 years ago
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
(Assignee)

Comment 3

13 years ago
Checking in nsDocAccessible.cpp;
/cvsroot/mozilla/accessible/src/base/nsDocAccessible.cpp,v  <--  nsDocAccessible.cpp
new revision: 1.39; previous revision: 1.38
done
You need to log in before you can comment on or make changes to this bug.