Issue metadata
Sign in to add a comment
|
F12 has to be pressed twice to close dev tools
Reported by
clon...@yahoo.com.au,
May 2 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 Safari/537.36 Steps to reproduce the problem: 1. Open dev tools on any page 2. Press F12 (nothing happens) What is the expected behavior? The dev tools should close immediately. What went wrong? The dev tools don't close until F12 is pressed a second time. Did this work before? Yes Chrome version: 66.0.3359.139 Channel: stable OS Version: 10.0 Flash Version:
,
May 2 2018
Bisect info: 534914 (good) - 534921 (bad) https://chromium.googlesource.com/chromium/src/+log/fa5073fc..e90821a3?pretty=fuller Suspecting r534915 = 023a553a5173570187cfc8f5cd620ea9db55d7f2 = https://crrev.com/c/897732 by elawrence@chromium.org "Add Focus Debuggee command to DevTools" Landed in 66.0.3343.0
,
May 2 2018
Able to reproduce the issue on Win-10 and Ubuntu 14.04 using chrome reported version #66.0.3359.139 but the same is not reproducible in the latest canary #68.0.3416.0. Issue is not applicable to OS-Mac. Reverse Bisect Information: ===================== Good build: 67.0.3396.0 Bad Build : 67.0.3395.0 Change Log URL: https://chromium.googlesource.com/chromium/src/+log/69c14cb6c480a7b36cb28a424561cb58faf992aa..61a99545b36d8d58bf5ee3929603630eedd2f246 From the above change log suspecting below change Change-Id: I6acd66e01ba9a8ef3a8a082bd18e7da569ff347f Reviewed-on: https://chromium-review.googlesource.com/1010469 elawrence@ - Could you please check and merge the fix to M-66 if it is a valid candidate. Adding label RBS as it seems to be a recent regression. Please feel free to remove the same if not appropriate. Thanks...!!
,
May 2 2018
This regression indeed went into M66 and the fix into M67. Unfortunately, it doesn't meet the severity bar for a merge to stable.
,
May 3 2018
Thanks for investigating this, guys! I'm new to reporting Chrome bugs; when you say "it doesn't meet the severity bar for a merge to stable", does that mean it won't be merged into M66 as a minor patch? That's totally reasonable, just curious about the terminology you're using since I don't know much about Chrome's repo management or development/deployment processes.
,
May 3 2018
Re #6: Thanks for the report. Chrome releases flow through "Channels" from Canary to Dev to Beta to Stable. At this time, Chrome 66 is the "stable" release that most of our users have. When a version is in the Stable channel, only very severe bugs (security issues, major crashes or functionality regressions) are fixed to help ensure the stability of the release. This issue wasn't discovered before Chrome 67 was branched from 66, and thus it was fixed only in Chrome 67. Chrome 67 is slated to reach the stable channel at the end of May. Apologies for the delay.
,
May 3 2018
Oh cool, I understand. It's only a minor annoyance haha :P
,
May 10 2018
Issue 841443 has been merged into this issue. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, May 2 2018