[Webkit-unassigned] [Bug 20632] WebKitWebFrame should be replaced with GdomFrame

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Sep 13 07:17:18 PDT 2008


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


alp at nuanti.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alp at nuanti.com




------- Comment #1 from alp at nuanti.com  2008-09-13 07:17 PDT -------
(In reply to comment #0)
> ... or the other way round.
> GdomFrame contains auto-generated the complete set of bindings, whereas
> WebKitWebFrame is manually created glib code.
> 

The core WebKit/GTK+ API is intentionally hand-written to provide a tailored
interface for developers. There isn't anything in the DOM that would work as a
good replacement for WebKitWebFrame without customisation so the convention in
WebKit ports is to provide accessors to the DOM binding from the core API
rather than trying to use the DOM directly for all interaction with the browser
engine.


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



More information about the webkit-unassigned mailing list