[Webkit-unassigned] [Bug 280402] New: WebKitTestRunner dump logic behaves differently in site isolation

[bugzilla-daemon at webkit.org]

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

            Bug ID: 280402
           Summary: WebKitTestRunner dump logic behaves differently in
                    site isolation
           Product: WebKit
           Version: WebKit Local Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: WebKit Process Model
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: kkinnunen at apple.com
                CC: nham at apple.com, webkit-bug-importer at group.apple.com

WebKitTestRunner dump logic behaves differently in site isolation

Cannot match non-site-isolation if the dump logic is different.

When run after onload, not in onload scope, notifyDone() will dump :
 - no site isolation: *at that moment*
 - site isolation: sometime in the future after exiting the call stack

forceImmediateCompletion() will dump:
 - no site isolation: *at that moment*
 - site isolation: sometime in the future after exiting the call stack


This is due to the fact that dumping needs to traverse the frames. On site isolation, individual frames cannot traverse frames.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20240926/3b2e491d/attachment-0001.htm>