275664 2024-06-19 06:19:01 -0700 Auto-open DevTools for popups 2025-10-03 05:20:34 -0700 1 1 1 Unclassified WebKit Web Inspector Safari 17 Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=247660 InRadar P2 Normal --- 1 opendarwin webkit-unassigned inspector-bugzilla-changes karlcow rcaliman webkit-bug-importer oldest_to_newest 2042108 0 opendarwin 2024-06-19 06:19:01 -0700 Add a new setting like Google Chrome's "Auto-open DevTools for popups" that automatically opens the web inspector in the new tab for window.open() and target="_blank" links when the web inspector is already open. Otherwise it's very difficult to debug page loading in the new tab, especially if there's any kind of redirect. 2042126 1 rcaliman 2024-06-19 09:50:15 -0700 This sounds useful. It's similar to the option to automatically open Web Inspector for JS Contexts in the Safari Develop menu. 2042127 2 webkit-bug-importer 2024-06-19 09:50:34 -0700 <rdar://problem/130157708> 2042149 3 karlcow 2024-06-19 16:13:50 -0700 Razvan, Jeff, I believe this is a duplicate of Bug 247660 2042151 4 opendarwin 2024-06-19 16:27:19 -0700 (In reply to Karl Dubost from comment #3) > Razvan, Jeff, I believe this is a duplicate of Bug 247660 They certainly seem similar, though I'm not sure I understand this part: "The importance is to be able to automatically continue the debugging journey." In one practical sense, you can continue because there's now a new tab open with the web inspector that you can debug (separately). In the sense of stepping through code, however, I'm not sure that you can continue? "Remote URLs won't load immediately. When window.open() returns, the window always contains about:blank. The actual fetching of the URL is deferred and starts after the current script block finishes executing. The window creation and the loading of the referenced resource are done asynchronously." https://developer.mozilla.org/docs/Web/API/Window/open 2042156 5 karlcow 2024-06-19 17:33:52 -0700 In a non-technical term. 1. let's say you click on a link which open a new window or tab to login to a third party 2. I want this to open automatically the web inspector in the new window 3. I want to be already in a step by step breakpoint scenario. 4. When the last step of the breakpoint is happening when the code is closing the window 5. I want to be able to continue the breakpoints as it was when I left. I understand it is a hard problem to solve. 2148120 6 rcaliman 2025-10-03 05:20:34 -0700 Karl, the two requests are independent. You're right that following a JS debugging session across contexts is a hard problem. But automatically opening a Web Inspector session for a popup and immediately pausing execution is solvable. There's a higher chance of getting this implemented instead of the cross-context debugging workflow.