WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
71770
Web Inspector: display notification in the front-end when inspected worker terminates
https://bugs.webkit.org/show_bug.cgi?id=71770
Summary
Web Inspector: display notification in the front-end when inspected worker te...
Yury Semikhatsky
Reported
2011-11-07 23:09:49 PST
When inspected worker terminates we should display a notification to let the user know that the worker has gone.
Attachments
Patch
(14.49 KB, patch)
2011-11-07 23:14 PST
,
Yury Semikhatsky
no flags
Details
Formatted Diff
Diff
Patch
(8.74 KB, patch)
2011-11-08 04:30 PST
,
Yury Semikhatsky
pfeldman
: review+
Details
Formatted Diff
Diff
Patch for landing
(7.74 KB, patch)
2011-11-08 04:56 PST
,
Yury Semikhatsky
no flags
Details
Formatted Diff
Diff
Show Obsolete
(2)
View All
Add attachment
proposed patch, testcase, etc.
Yury Semikhatsky
Comment 1
2011-11-07 23:14:19 PST
Created
attachment 113996
[details]
Patch
WebKit Review Bot
Comment 2
2011-11-07 23:17:19 PST
Please wait for approval from
fishd@chromium.org
before submitting because this patch contains changes to the Chromium public API.
Pavel Feldman
Comment 3
2011-11-07 23:27:44 PST
Comment on
attachment 113996
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=113996&action=review
We have a similar scenario in the remote debugging: front-end should display "disconnected / terminated" message upon socket close event. You should wire that event to the disconnected screen as well.
> Source/WebCore/inspector/front-end/HelpScreen.js:57 > +WebInspector.HelpScreen.visibleScreen_ = null;
Could you extract this refactoring into a separate change?
> Source/WebKit/chromium/src/WebDevToolsFrontendImpl.h:69 > + virtual void agentDestroyed();
It might be that we disconnected from the agent, it is not necessarily destroyed. At least in the downstream case, I would use "disconnect", not "destroy".
Yury Semikhatsky
Comment 4
2011-11-07 23:33:56 PST
Comment on
attachment 113996
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=113996&action=review
>> Source/WebKit/chromium/src/WebDevToolsFrontendImpl.h:69 >> + virtual void agentDestroyed(); > > It might be that we disconnected from the agent, it is not necessarily destroyed. At least in the downstream case, I would use "disconnect", not "destroy".
If we need to listen to regular disconnect event there should be a separate method. This one is only called when inspected instance is actually destroyed.
Darin Fisher (:fishd, Google)
Comment 5
2011-11-08 00:50:02 PST
(In reply to
comment #2
)
> Please wait for approval from
fishd@chromium.org
before submitting because this patch contains changes to the Chromium public API.
I defer to pfeldman's review here.
Yury Semikhatsky
Comment 6
2011-11-08 04:30:11 PST
Created
attachment 114038
[details]
Patch
Pavel Feldman
Comment 7
2011-11-08 04:49:04 PST
Comment on
attachment 114038
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=114038&action=review
> Source/WebCore/inspector/front-end/inspector.js:464 > + WebInspector.log("disconnectFromBackend");
Please remove this trace.
> Source/WebCore/inspector/front-end/inspector.js:857 > + WebInspector.log("frontendReused");
ditto
> Source/WebKit/chromium/public/WebDevToolsAgent.h:95 > + WEBKIT_EXPORT static WebString createFrontendDisconnectedEvent();
disconnectEventAsText() ?
Yury Semikhatsky
Comment 8
2011-11-08 04:56:29 PST
Created
attachment 114041
[details]
Patch for landing All comments addressed.
Yury Semikhatsky
Comment 9
2011-11-08 05:06:53 PST
Committed
r99554
: <
http://trac.webkit.org/changeset/99554
>
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug