[Webkit-unassigned] [Bug 30113] New: Adding webkit_init to the API instead of calling it inside the class_init functions

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Oct 6 02:10:48 PDT 2009


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

           Summary: Adding webkit_init to the API instead of calling it
                    inside the class_init functions
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: All
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: WebKit Gtk
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: alex at igalia.com
                CC: xan.lopez at gmail.com


We have found some situations where doing the transparent initialization of the
class_init functions is not enough, for instance when a program starts creating
a KURL, the developers would have to call other function that calls the init
before creating the object. This is causing problems like the one in the bug
28947, which could be in other parts of the library API.

The option that could fix this problem is adding the init function to the API
and asking the developers to call it before using any API function.

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



More information about the webkit-unassigned mailing list