Looking at liferea code I've noticed that they use
WebKitWebView::hovering-over-link signal (ephy uses it too). This signal
comes from ChromeClient::mouseDidMoveOverElement() and I was wondering
whether it would be useful to expose it as a general signal in the API,
instead of just for links.
El vie, 27-01-2012 a las 14:56 +0100, Carlos Garcia Campos escribió:
Looking at liferea code I've noticed that they use
WebKitWebView::hovering-over-link signal (ephy uses it too). This signal
comes from ChromeClient::mouseDidMoveOverElement() and I was wondering
whether it would be useful to
On Fri, Jan 27, 2012 at 5:56 AM, Carlos Garcia Campos
cgar...@igalia.com wrote:
That also made me think about how to expose HitTestResult in the API. In
WebKit1 it's only used by webkit_web_view_get_hit_test_result() (it
sounds like a getter, but it actually performs a hit test and returns
the
El vie, 27-01-2012 a las 06:11 -0800, Martin Robinson escribió:
We could use a similar approach than WK1 HitTestResult object, it has
flags to get information about the hoevered thing (whether it's a link,
or image, or text selected, whether the area is editable, etc.) and the
uri or the
On 01/27/2012 02:56 PM, Carlos Garcia Campos wrote:
Looking at liferea code I've noticed that they use
WebKitWebView::hovering-over-link signal (ephy uses it too). This signal
comes from ChromeClient::mouseDidMoveOverElement() and I was wondering
whether it would be useful to expose it as a
