VoiceOver can't navigate this page because Safari is used absoluteFocusRingQuads() to calculate the size of the web area, which descends into every child element and sums up the rectangles. http://www.siye.co.uk/siye/viewstory.php?action=printable&textsize=0&sid=12548&chapter=all#top I think the web area should not use absoluteFocusRingQuads(), but absoluteQuads() instead
Created attachment 61441 [details] patch
Created attachment 61442 [details] patch
Comment on attachment 61442 [details] patch > + // absoluteFocusRingQuads will query the hierarchy below this element, which for large webpages can be very slow. > + // For a web area, which will have the most elements of any element, absoluteQuads should be used. Are there any other cases where absoluteQuads would be better? Should absoluteFocusRungQuads itself have an optimization for this case? r=me
(In reply to comment #3) > (From update of attachment 61442 [details]) > > + // absoluteFocusRingQuads will query the hierarchy below this element, which for large webpages can be very slow. > > + // For a web area, which will have the most elements of any element, absoluteQuads should be used. > > Are there any other cases where absoluteQuads would be better? Should absoluteFocusRungQuads itself have an optimization for this case? > I was trying to think of other cases that might be pertinent (AXGroups being the best candidate), but it seemed more prudent to wait for evidence of those cases than make assumptions here. I looked through absoluteFocusRingQuads and given that the nature of the function seems to iterate every child, it didn't look like there was much that could be done (since there are over 15000 children of this web area). If you have any ideas off the top of your head please let me know. > r=me
http://trac.webkit.org/changeset/63350