[Webkit-unassigned] [Bug 53868] New: [Qt] fast/notifications/notifications-document-close-crash.html fails after r77738

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sun Feb 6 02:42:03 PST 2011


           Summary: [Qt]
                    html fails after r77738
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Mac OS X 10.5
            Status: NEW
          Keywords: Qt, QtTriaged
          Severity: Normal
          Priority: P2
         Component: WebKit Qt
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: robert at webkit.org

Fails after http://trac.webkit.org/changeset/77738

-CONSOLE MESSAGE: line 36: INVALID_STATE_ERR: DOM Exception 11: An attempt was made to use an object that is not, or is no longer, usable.
+CONSOLE MESSAGE: line 36: TypeError: Type error

Failure is because of:

JSValue JSNotificationCenter::requestPermission(ExecState* exec)
    ScriptExecutionContext* context = impl()->scriptExecutionContext();

    // Make sure that script execution context is valid.
    if (!context) {
        setDOMException(exec, INVALID_STATE_ERR);
        return jsUndefined();
    if (!exec->argument(0).isObject())
        return throwTypeError(exec);


'context' above used to be a local copy of ActiveDomObject::scriptExecutionContext() but is now the scriptExectionContext() (an upcast of Document) for the page's Document object.

On Qt, apparently unlike other platforms, this context object is not destroyed by the time the test calls requestPermission(), so instead Qt fails in the above function at 'if (!exec->argument(0).isObject())' instead.

Not clear to me why this is happening only for Qt, so skipping for now.

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