[Webkit-unassigned] [Bug 205484] New: Web Inspector: Cannot interact with JSContext except during auto-break on connect

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Dec 19 20:16:40 PST 2019


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

            Bug ID: 205484
           Summary: Web Inspector: Cannot interact with JSContext except
                    during auto-break on connect
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Macintosh
                OS: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: Web Inspector
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: ross.kirsling at sony.com
                CC: inspector-bugzilla-changes at group.apple.com

This is difficult to summarize, but here goes nothing.
I would assume I'm missing some fundamental expectation, except that I'm sure I've seen this "just work" in the past...?

Repro:
1. Launch Safari (see notes).
2. From the Develop menu, set "Automatically Show Web Inspector for JSContexts" (for convenience).
   Don't set "Automatically Pause Connecting to JSContexts" yet.
3. Run `run-jsc --remote-debug`. REPL or long-running script doesn't seem to matter; I'll just assume the former here.
4. Web Inspector appears automatically; attempt to click pause on Sources or record on Timelines.

A. Nothing happens! \(^o^)/
   Whatever you clicked turned to a grey state, but otherwise WI just sits there (even as you continue to do stuff on the REPL).

5. Kill JSC, set "Automatically Pause Connecting to JSContexts", re-run JSC.
6. Web Inspector appears automatically; hit record if you'd like a timeline, then type something into the REPL.

B. Auto-break! We can step-debug and use the console freely for one glorious moment. Even timelines sort of works if you hit record before.

7. Eventually, hit the play button, then return to step 4 / outcome A.

Notes:
Ideally we'd use `run-safari` but that greys out the Develop menu, so I used latest STP.
(Even more ideally would be `run-minibrowser`, but to my knowledge that doesn't allow for JSContext inspection.)

-- 
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/20191220/fd490a6d/attachment.htm>


More information about the webkit-unassigned mailing list