[Webkit-unassigned] [Bug 99578] [EFL] Share WebKit-Gtk's Accessibility implementation with others WebKit ports.

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=99578





--- Comment #16 from Krzysztof Czech <k.czech at samsung.com>  2012-11-05 02:44:30 PST ---
This common module "atk" will not have any specific port dependency, the only dependency is glib, but we are OK with it, regarding what has been said about it.

Well, yes EFL as a framework has some support for Accessibility, but not in terms of ATK and WebKit.
WebKit-GTK had already done that. Mappings to atk are already implemented and as Alejendro said they're are going to be improved. The only thing we (EFL developers) should take care of, are toolkit differences in terms of proper communication with EFL.
(In reply to comment #15)
> (In reply to comment #14)
> > (In reply to comment #13)
> > 
> > > So, in a nutshell, if the EFL port is willing to reuse the ATK implementation of WebKitGTK+ it needs to keep Glib. Other option is to go ahead and implement their own "ATK-like thing", if it's not there yet, or to go and speak directly with the AT-SPI world from EFL's widget library. That's what they do in Qt with their atspi-qt bridge I think.
> > 
> > It's also important to keep in mind that EFL has an implicit dependency on GLib anyway via the libsoup backend.
> 
> If ATK depends on glib, EFL port also should use glib as libsoup case.  I just thought common module should not have specific port dependency. If this is able to be allowed, I don't mind.
> 
> 
> Krzysztof, 
> 
> As we know, EFL itself is going to support a library for accessibility. Will you use ATK for EFL port though ?

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