[Webkit-unassigned] [Bug 25411] [GTK] ATK accessible ancestry broken

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Oct 18 11:45:27 PDT 2009


--- Comment #9 from Xan Lopez <xan.lopez at gmail.com>  2009-10-18 11:45:27 PDT ---
(In reply to comment #7)
> (In reply to comment #6)
> > (From update of attachment 41372 [details] [details])
> > So, my only concern is that it seems to me with this patch you basically need
> > to always have called ref_child for get_parent to work. Is this OK?
> Heck, I was hoping you knew. ;-) I'm still finding my way around the code, so
> to be honest, I'm not sure.
> What happens when a document is loaded in WebKit? If the process is that a
> document loads and an accessible version of the document is rendered from the
> top down, I think this would be OK. If instead, nothing gets rendered until the
> user interacts with it, then, no, it wouldn't be OK.

So, what I really meant is how applications like Orca use the ATK APIs. If
there's any chance than get_parent would be called before ref_child then the
patch is wrong, as get_parent would return NULL. AFAIK WebKit constructs the
DOM tree when the page is loaded, and the a11y tree is constructed on-demand
when the a11y APIs are called.

But since you think the patch is wrong anyway we'll clear the queue.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list