Summary: | AX: need a way to get the progress of a webpage load | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | chris fleizach <cfleizach> | ||||
Component: | Accessibility | Assignee: | chris fleizach <cfleizach> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | bdakin, darin, eric, webkit.review.bot | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Attachments: |
|
Description
chris fleizach
2010-01-05 10:57:05 PST
Created attachment 45917 [details]
patch
This patch caused some changes in some other tests.
I decided to rewrite frame-with-title.html to be more modern and precise.
style-queue ran check-webkit-style on attachment 45917 [details] without any errors.
Comment on attachment 45917 [details]
patch
Tab:
+ shouldBe("obj.isAttributeSupported('AXLoadingProgress')", "true");
I'm surprised that AX exposes this sort of data!
AXLayoutCount: 2
+AXLoadingProgress: 1
At least the "layout count" is shocking. :)
LGTM.
Filed a bug about check-webkit-style not noticing the tab: bug 33227 > I'm surprised that AX exposes this sort of data!
Yea, users want to be able to know the percentage of load completion for webpages. Visually you can see that, but if you're just listening for when the page completely loads, it can be frustrating not knowing the progress
(In reply to comment #3) > AXLayoutCount: 2 > +AXLoadingProgress: 1 AXLayoutCount is a way to allow the screen reader to have a clue for when the page might have changed enough to invalidate what it knows about the elements on the page. There might be a better way. It was invented years back to get VoiceOver working well. |