☂ DevTools: Execution Context Selector switches to incorrect context
Reported by
antonio....@gmail.com,
Nov 16 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. install Vimium chrome extension. 2. Load any page. 3. Open console in dev tools. 4. Find the 'vomnibar.html' frame is selected in the Execution Context Selector. What is the expected behavior? I expect the top frame to be selected as it usually is when the Vimium extension is not in use. What went wrong? It slows down development if I want to make use of the Vimium extension and use the console, because I must manually select the 'top' frame in the Execution Context Selector. WebStore page: https://github.com/philc/vimium/issues/2805 Did this work before? N/A Chrome version: 61.0.3163.100 Channel: n/a OS Version: OS X 10.12.6 Other cases: What steps will reproduce the problem? (1) Open a site with a iFrame that runs JS, open DevTools without loading Elements Panel (2) Add breakpoint in the iFrame's JS and pause there (3) Observe that the console context selector switches to iFrame context on pause (4) Evaluate any node in console (e.g. `document.body`) Expected: Console context should stay on iFrame context Actual: Console context switches to 'top' Another symptom with the same cause: - Open newtab page - Right click, inspect an element - Set a breakpoint in the iFrame - Refresh to pause on the breakpoint Expected: context selector should be the iframe Actual: context selector switches to 'top'
,
Nov 17 2017
Able to reproduce this issue on reported version 61.0.3163.100 , on latest stable 62.0.3202.94 and on latest canary 64.0.3271.0 using Mac 10.12.6, Windows 10 and Ubuntu 14.04 with steps mentioned in comment#0. i.e;Vimium is seen instead of 'top' frame in console. This issue is seen from M50. [50.0.2661.0]. Hence considering this issue as Non-regression and marking as Untriaged
,
Nov 17 2017
Thanks for the report. I can reproduce with Vimium and with another extension that loads an iframe. Looks like any time there is an out-of-process-iframe (oopif) on a page, DevTools loads them after the main frame, leading the console to think it should switch to that context.
,
Dec 8 2017
,
Dec 8 2017
,
Dec 8 2017
,
Jan 30 2018
After testing on Mac 66.0.3334.0, it looks like all the cases are no longer reproducible. I believe this is a result of the recent experiment to render OOPIF-frames inline (https://chromium-review.googlesource.com/c/chromium/src/+/877504) so marking this as fixed. If you are still able to reproduce the issue on Canary, please let us know. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 Deleted