[Webkit-unassigned] [Bug 200114] Web Inspector: Debugger: don't allow the domain to be disabled

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Aug 9 13:55:39 PDT 2019


https://bugs.webkit.org/show_bug.cgi?id=200114

Yury Semikhatsky <yurys at chromium.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yurys at chromium.org

--- Comment #1 from Yury Semikhatsky <yurys at chromium.org> ---
I wonder about the direction of removing enable/disable methods from protocol domains in general, what is the rationale for that? Does it mean that a client will now be receiving all events upon connection?

In the past we stuck to the principle of radio silence in the protocol by default, i.e. no events were sent over the wire until a domain was explicitly enabled. This was useful for low overhead instrumentation, e.g. when recording CPU profile it would make sense to disable things like debugger, DOM etc which could have non-trivial performance impact. What is the story for such use cases going forward?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20190809/23ab0dca/attachment.html>


More information about the webkit-unassigned mailing list