You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Console.enable should not error since console is in the js_protocol.json domain
Response id's should be whole numbers not 1.0000. It doesn't break javascript but adds extra bytes on the websocket pipe when can be avoided. The other ids like startLine, endLine and executionContextId also have similar issues which can add up.
Chrome has the same problem so I'm guessing it needs to be fixed in v8 land.
Activity
pavelfeldman commentedon Jul 14, 2016
Filed https://bugs.chromium.org/p/chromium/issues/detail?id=628389 upstream.
nojvek commentedon Jul 14, 2016
Filed the console issue separate as well
https://bugs.chromium.org/p/chromium/issues/detail?id=628390
deps: update v8_inspector