El mié, 13-08-2014 a las 15:05 -0400, Victor Lucero escribió: > I just read the links you provided . > > I now need to setup a extension to get access to the WebPage so i can get > access to the web frame an his js context. > thats nice but i also need access to all the frames in the current page. will > this be exposed in any way in the near future?
There are no plans to expose it unless there's a real need. So, file a bug report and explain your use case there. > To me is very important because the kinds of tasks we produce are inside the > context of every frame. If we are talking about the WebExtensions API, things are easier because we already have a WebKitFrame object there. > > El 13-08-2014, a las 13:27, Sami Wagiaalla <[email protected]> escribió: > > > > >> in the prior version of webkitgtk api(version 1) i got all these useful > >> signals. but in api2 they are gone :( > >> > >> does they exist inside Webkit2 and just aren’t exposed by the Gtk api? > >> > > > > Most are still present. Some have been renamed, and some have been moved to > > the core and can only be accessed through the extension architecture; > > details here [1]. > > > > You can ask here, or look through the documentation index [2] for the > > specific signals you need. > > > > [1] > > http://blogs.igalia.com/carlosgc/2013/09/10/webkit2gtk-web-process-extensions/ > > [2] http://webkitgtk.org/reference/webkit2gtk/stable/index-all.html > -- Carlos Garcia Campos http://pgp.rediris.es:11371/pks/lookup?op=get&search=0xF3D322D0EC4582C3
signature.asc
Description: This is a digitally signed message part
_______________________________________________ webkit-gtk mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-gtk
