[Webkit-unassigned] [Bug 33785] [Gtk] AtkHyperlink needs to be implemented
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Sep 27 09:56:22 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=33785
--- Comment #5 from Mario Sanchez Prada <msanchez at igalia.com> 2010-09-27 09:56:22 PST ---
(In reply to comment #2)
> Hi Joanie, I was wondering how precisely to do this. So far I can see that different
> AtkInterfaces are implemented/enabled depending on the role detected on object
> creation time. But I wonder what to do with the AtkHyperlink *object*.
Same doubts here. As long as I could figure it out so far, it looks to me that a new class would be needed to be implemented as a subclass of AtkHyperLink, which would hold references to WebKitAccessible objects implementing the AtkHyperlinkImpl *interface*, so calling to the methods like atk_hyperlink_get_uri(int index) would actually return the desired value.
> I'm a bit clueless of where or what other objects -not interfaces- are implemented
> or where would I fit this.
If possible, I think the way to go here would be to somehow implement it inside the wrapper file as well, or in another one inside the gtk/ directory, but that would "break" the common layout for all the ports (platform specific versions of AXObjectCache, AccessibilityObject and AccessibilityObjectWrapper only).
> I'm wondering if it should be in accesibility/ as a new file or if it's something only
> relevant for gtk/.
I don't see anything in cross-platform code similar to the structure we need in here (HyperText - HyperLink - link) so I guess going for gtk specific code would be the way to go at this moment.
> I'm discovering a new world.
Me too :-O
--
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