On Wed, Jun 22, 2011 at 4:21 PM, Chris Fleizach <cfleiz...@apple.com> wrote: > I think this is one drawback of Chrome's approach, the inability to retrieve > dynamic information. I suspect Chrome has similar issues for the > NSAccessibilityParameterizedAttribute attributes, and that it doesn't support > the AXTextMarker APIs that Safari does for the same reason. > > To support this (along with the other things I mentioned) Chrome would need > to synchronously called into WebCore, wait for the answer, and then return > that information.
Yes, we're open to doing this where necessary. > Yes, WebKit2 works with accessibility. You'll be able to see the code to > support that strewn throughout WebKit2. Let me know if you need more pointers. I'll take a closer look, thanks. - Dominic _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
