New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 592132 link

Starred by 2 users
Status: Archived
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Cache not cleared in No-Cache-Mode by Iframe reload

Reported by framefra...@gmail.com, Mar 4 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.75 Safari/537.36

Steps to reproduce the problem:
1. Just start Debugging on a Iframe, Change your code and reload it multiple times.

What is the expected behavior?
Scripts/Resources in the Iframe should be refreshed, Cache cleared.

What went wrong?
Scripts are "collected" and get more and more. The actual Script (which I want to debug) is not refreshed and shows the old source. Sometimes the runtime gets the current source while the debugger shows the old one.

Did this work before? No 

Chrome version: 49.0.2623.75  Channel: beta
OS Version: 10.0
Flash Version: Shockwave Flash 20.0 r0

The No-Cache-Mode should cache nothing, even removed breakpoints re-appear - which is very annoying.

Comment 1 Deleted

Comment 2 by framefra...@gmail.com, Mar 4 2016 

The Resources-Tab shows the current right loaded script, the debugger the old one.

Comment 3 by framefra...@gmail.com, Mar 4 2016 

Should add: There are the same scripts in multiple frames, but each script is bound to the document in each frame and the debugger should show the right source anyway.

Comment 4 by alph@chromium.org, Mar 8 2016

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 5 by pfeldman@chromium.org, Oct 5 2017

Status: Archived (was: Assigned)
Bulk DevTools triage, closing low priority issues with no action plan.
►

Sign in to add a comment