191852 2018-11-19 23:00:17 -0800 Web Inspector: REGRESSION(r238330): 'Timeline' domain was not found 2018-11-30 13:19:44 -0800 1 1 1 Unclassified WebKit Web Inspector WebKit Nightly Build All All RESOLVED CONFIGURATION CHANGED InRadar P2 Normal --- 191740 1 hi joepeck hi inspector-bugzilla-changes joepeck webkit-bug-importer oldest_to_newest 1480391 0 hi 2018-11-19 23:00:17 -0800 Every time I open WebInspector, with the Timelines tab showing, I see an error in the console: CONSOLE ERROR Unhandled Promise Rejection: Error: 'Timeline' domain was not found This also prevents auto-capture on page navigation from working properly. This error does not appear if the Timelines tab is was not previously showing. 1481575 1 hi 2018-11-26 10:26:47 -0800 I'm also seeing this happen for "DOMDebugger": .../Release/WebInspectorUI.framework/Resources/Protocol/Connection.js:101:30: CONSOLE ERROR Request with id = 1 failed. {"code":-32601,"message":"'DOMDebugger' domain was not found","data":[{"code":-32601,"message":"'DOMDebugger' domain was not found"}]} .../Release/WebInspectorUI.framework/Resources/Controllers/DOMDebuggerManager.js:461:30: CONSOLE ERROR 'DOMDebugger' domain was not found 1482021 2 webkit-bug-importer 2018-11-27 11:58:18 -0800 <rdar://problem/46283531> 1483122 3 joepeck 2018-11-29 13:19:38 -0800 I'm not seeing these in a Release build (r238660). Are you still seeing this? 1483165 4 hi 2018-11-29 14:03:15 -0800 I'm not seeing this error anymore, but I am still not seeing auto-capture working properly. * STEPS TO REPRODUCE: 1. inspect <https://webkit.org> 2. show Timelines tab 3. refresh the page (timeline auto-capture will start) 4. wait for timeline to stop capturing (or manually stop it) 5. navigate to <https://apple.com> => auto-capture didn't start => refreshing the page will not start auto-capture 1483174 5 joepeck 2018-11-29 14:11:54 -0800 (In reply to Devin Rousso from comment #4) > I'm not seeing this error anymore, but I am still not seeing auto-capture > working properly. Correct auto-capture is a separate issue that I'll be looking into. 1483701 6 joepeck 2018-11-30 13:19:35 -0800 (In reply to Joseph Pecoraro from comment #5) > (In reply to Devin Rousso from comment #4) > > I'm not seeing this error anymore, but I am still not seeing auto-capture > > working properly. > > Correct auto-capture is a separate issue that I'll be looking into. Bug 192248. Lets close this I'm not seeing it anymore so I think we've addressed it (likely fixing InspectorFrontendAPI ordering).