Bug 191852
| Summary: | Web Inspector: REGRESSION(r238330): 'Timeline' domain was not found | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Devin Rousso <hi> |
| Component: | Web Inspector | Assignee: | Joseph Pecoraro <joepeck> |
| Status: | RESOLVED CONFIGURATION CHANGED | ||
| Severity: | Normal | CC: | hi, inspector-bugzilla-changes, joepeck, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | All | ||
| OS: | All | ||
| Bug Depends on: | 191740 | ||
| Bug Blocks: | |||
Devin Rousso
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.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Devin Rousso
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
Radar WebKit Bug Importer
<rdar://problem/46283531>
Joseph Pecoraro
I'm not seeing these in a Release build (r238660). Are you still seeing this?
Devin Rousso
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
Joseph Pecoraro
(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.
Joseph Pecoraro
(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).