Issue metadata
Sign in to add a comment
|
chrome auto-updated a new devtools (I got "what's new..." n console area), now I get mouse move errors when moving between inspector and web page, see attachment.
Reported by
barrysh...@gmail.com,
Jun 7 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36 Steps to reproduce the problem: 1. Open inspector (right click etc) 2. Move mouse between inspector and web page 3. stops with "paused in debugger" in an extension, typerror: cannot read property startContainer (in a mouse event, not mine, the extensions', various extensions, nothing fancy, lazarus, perapera chinese dictionary, nothing I wrote or recently loaded.) What is the expected behavior? That I can move the mouse between the inspector and the web page being debugged without exceptions every time. What went wrong? Move mouse between inspector and web page and get typerror: cannot read property startContainer instantly, pauses in debugger repeatedly. Totally unusable, just exceptions on mouse motion between inspector and web page every time. See attachment. Did this work before? Yes Version of what, devtools? I don't know but it seems to automatically update as it did which caused this breakage so I guess the previous version to the past 24 hours or less. Chrome version: 59.0.3071.86 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: How do I downgrade devtool version so I can work? Is it possible? Note: I tried disabling extensions, I don't have many, disabling one would just cause the same error in another extension. I suppose I could try disabling all extensions, I am not very dependent on them but I am pessimistic that will fix anything, maybe. I can try it, not that much trouble but this is some sort of problem with the new devtools. Note I was using devtools just fine less than 24 hours ago (it is now 7 June 2017 00:56 ET, Boston, MA, US), I was using devtools until about 3 AM without this problem, same project, same tab, just switched to that tab to work and saw there was a new devtools and this problem started. As I said I did get a message in the console area about "What's new" indicating a new devtools had been loaded recently and this error immediately started.
,
Jun 10 2017
FWIW disabling: Zhongwen: Chinese-English Dictionary 4.8 (available from chrome app store) seemed to stop the problem. I went thru each extension I had, only about 10, one by one disabling each, test above bug, etc went away when I disabled the above ext. I re-enabled that ext and the problem reappeared so I'd call that a smoking gun but why it used to work is anyone's guess. I don't really need that ext anyhow but maybe this will save some other child lost in the wilderness... The problem with software is too many moving parts -- Barry Shein
,
Jun 11 2017
And I had to disable Lazarus (also available from the app store) when the same problem started again.
,
Jun 19 2017
It sounds you've been able to fix your issue by disabling a couple of extensions that were throwing exceptions. DevTools upgrades as the same time as Chrome (since it's part of the binary) so it might've been that some APIs changed which caused your extensions to throw an exception but this is speculation. I'll mark this issue as closed since I'm not sure what else we can do on our end. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by barrysh...@gmail.com
, Jun 7 2017