Bug 33221 - AX: need a way to get the progress of a webpage load
Summary: AX: need a way to get the progress of a webpage load
Alias: None
Product: WebKit
Classification: Unclassified
Component: Accessibility (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: chris fleizach
Depends on:
Reported: 2010-01-05 10:57 PST by chris fleizach
Modified: 2010-01-05 12:33 PST (History)
4 users (show)

See Also:

patch (12.97 KB, patch)
2010-01-05 12:07 PST, chris fleizach
eric: review+
eric: commit-queue-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description chris fleizach 2010-01-05 10:57:05 PST
VoiceOver needs a way to get the progress of a webpage load.
Comment 1 chris fleizach 2010-01-05 12:07:47 PST
Created attachment 45917 [details]

This patch caused some changes in some other tests. 

I decided to rewrite frame-with-title.html to be more modern and precise.
Comment 2 WebKit Review Bot 2010-01-05 12:13:03 PST
style-queue ran check-webkit-style on attachment 45917 [details] without any errors.
Comment 3 Eric Seidel (no email) 2010-01-05 12:20:01 PST
Comment on attachment 45917 [details]

+	  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. :)

Comment 4 Eric Seidel (no email) 2010-01-05 12:21:52 PST
Filed a bug about check-webkit-style not noticing the tab: bug 33227
Comment 5 chris fleizach 2010-01-05 12:23:43 PST
> 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
Comment 6 Darin Adler 2010-01-05 12:26:51 PST
(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.
Comment 7 chris fleizach 2010-01-05 12:33:08 PST