-
Notifications
You must be signed in to change notification settings - Fork 15.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
devtools: api to inspect service worker #1719
Conversation
with next update for chromium we get better observers for service wokers |
/cc @paulcbetts , @hokein thoughts ? |
Into it! |
@@ -317,6 +317,17 @@ void NativeWindow::InspectElement(int x, int y) { | |||
agent->InspectElement(x, y); | |||
} | |||
|
|||
void NativeWindow::InspectServiceWorker() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why adding InspectServiceWorker
for NativeWindow
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
to support BrowserWindow.inspectServiceWorker
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is BrowserWindow.inspectServiceWorker
needed? I think we can just use window.webContents.inspectServiceWorker
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All the devtools api we have listed are on BrowserWindow
besides if they use window.webcontents
before its finished loading wouldnt webcontents.opendevtools
crash ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
devtools: api to inspect service worker
Fixes #1331
Depends on electron-archive/brightray#107