[Webkit-unassigned] [Bug 77835] [GObject bindings] EventListeners as first-class GObjects: WebKitDOMEventListener

[bugzilla-daemon at webkit.org]

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


C Anthony <anthony at xtfx.me> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[GObject bindings] Missing  |[GObject bindings]
                   |scope annotations for       |EventListeners as
                   |add/remove_event_listener   |first-class GObjects:
                   |                            |WebKitDOMEventListener




--- Comment #32 from C Anthony <anthony at xtfx.me>  2012-03-12 12:55:04 PST ---
ill update the patch tonight with test cases completed, and Changelog (using Tools/Scripts/webkit-patch and friends)

in case it wasn't clear, i enabled the attribute-based handlers; this almost doubles the size of the GIR file (~2600l -> 4300+) and adds *many* new properties to all the objects.

personally, i find the attributes based ones convenient, *and* there is never a risk of accidentally "losing" your handler.  this works (python):

listener = doc.create_event_listener(_onload_cb)
window.set_onload(listener)

... perfectly! albeit this:

listener = doc.create_event_listener(_onload_cb)
window.props.onload = listener

... does not.  IIRC it complained about wrong GType ID, then segfaulted at some point. however, it's seems likey this is a pygobject problem since it work just fine the other way; will dig more tonight when i create the testcases in C.

the question is ...

*do we want to expose attribute handlers?*

:-D yay! <- awesome! me too!
:-( nay. <- oh ... i, uh, agree.

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