Devtools should maintain frame context when refreshing page
Reported by
iamcraig...@gmail.com,
May 5 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: 1. Go to a page that has an embedded iframe on it 2. Select the frame from the context dropdown in the developer tools console 3. Refresh page What is the expected behavior? The frame you selected should stick until you close the tab or navigate away from the page What went wrong? It always defaults to the top page Did this work before? No Chrome version: 50.0.2661.94 Channel: stable OS Version: OS X 10.11.1 Flash Version: Shockwave Flash 21.0 r0 This is more of a UX question, but I find that when developing/testing embedded content it is frustrating that every time I refresh the page to test changes I have to manually select the iframe in the console.
,
Jul 7 2016
Related: #626415
,
Jul 7 2016
Good idea, but what about granularity? Is this per domain? Per page? I can think of pros and cons for both.
,
Jul 7 2016
I obviously do not work on the Chrome team, but I think it should be per devtools session the same way as bandwidth throttling. I think having it be sticky per domain will not really work well. Consider this case: - You are on a page with an embedded video in an iframe on it. You select the frame for that video cause you are debugging something - If you navigate to a different page that does not have an iframe it would be strange to go back to top so then some pages on the domain would change contexts and some would not If it is sticky per devtools session then you do not have that problem.
,
Jul 8 2016
,
Jul 8 2016
,
Oct 5 2017
Bulk DevTools triage, closing low priority issues with no action plan. |
||||
►
Sign in to add a comment |
||||
Comment 1 by alph@chromium.org
, May 6 2016Status: Assigned (was: Unconfirmed)