<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div apple-content-edited="true">El 14-08-2014, a las 3:23, Carlos Garcia Campos <<a href="mailto:cgarcia@igalia.com">cgarcia@igalia.com</a>> escribió:</div><div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">El mié, 13-08-2014 a las 15:05 -0400, Victor Lucero escribió:<br><blockquote type="cite">I just read the links you provided .<br><br>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.<br>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?<br></blockquote><br>There are no plans to expose it unless there's a real need. So, file a<br>bug report and explain your use case there.<br><br></div></blockquote><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite">To me is very important because the kinds of tasks we produce are inside the context of every frame.<br></blockquote><br>If we are talking about the WebExtensions API, things are easier because<br>we already have a WebKitFrame object there.<br></div></blockquote><div><br></div><div>That means that if We file a new bug asking for signal to get all the frames may be a possibility?.</div><div>because I don’t mind writing as a WebExtension at all if its for the sake of performance.</div><br><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><blockquote type="cite"><br>El 13-08-2014, a las 13:27, Sami Wagiaalla <<a href="mailto:swagiaal@redhat.com">swagiaal@redhat.com</a>> escribió:<br><br><blockquote type="cite"><br><blockquote type="cite">in the prior version of webkitgtk api(version 1) i got all these useful signals. but in api2 they are gone :(<br><br>does they exist inside Webkit2 and just aren’t exposed by the Gtk api?<br><br></blockquote><br>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].<br><br>You can ask here, or look through the documentation index [2] for the specific signals you need.<br><br>[1] <a href="http://blogs.igalia.com/carlosgc/2013/09/10/webkit2gtk-web-process-extensions/">http://blogs.igalia.com/carlosgc/2013/09/10/webkit2gtk-web-process-extensions/</a><br>[2] <a href="http://webkitgtk.org/reference/webkit2gtk/stable/index-all.html">http://webkitgtk.org/reference/webkit2gtk/stable/index-all.html</a><br></blockquote><br></blockquote><br>--<span class="Apple-converted-space"> </span><br>Carlos Garcia Campos<br><a href="http://pgp.rediris.es:11371/pks/lookup?op=get&search=0xF3D322D0EC4582C3">http://pgp.rediris.es:11371/pks/lookup?op=get&search=0xF3D322D0EC4582C3</a></div></blockquote></div><br></body></html>