Closed
Bug 244776
Opened 20 years ago
Closed 20 years ago
Don't fire page loading events when jumping to named anchor
Categories
(Core :: Disability Access APIs, defect)
Core
Disability Access APIs
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
Details
(Keywords: access)
Attachments
(1 file)
|
845 bytes,
patch
|
pkwarren
:
review+
darin.moz
:
superreview+
|
Details | Diff | Splinter Review |
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•20 years ago
|
||
|
|
Assignee | |
Updated•20 years ago
|
Attachment #149365 -
Flags: review?(pkw)
|
||
Comment 2•20 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•20 years ago
|
Attachment #149365 -
Flags: superreview?(darin)
|
||
Updated•20 years ago
|
Attachment #149365 -
Flags: superreview?(darin) → superreview+
|
|
Assignee | |
Updated•20 years ago
|
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 3•20 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.
Description
•