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

Issue 639001 link

Starred by 1 user
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Closed: Oct 31
Cc:
l...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Cannot disable dynamically added CSS declarations on a selected element across refreshes

Project Member Reported by phistuck@gmail.com, Aug 18 2016 
UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Go to data:text/html,<!doctype html><body><div id="a">a</div><script>setTimeout(function() { document.body.style.backgroundColor = "black"; document.querySelector("#a").style.backgroundColor = "blue";}, 1000)</script>
2. Press F12.
3. Go to the Elements panel.
4. Disable background-color: black on <body> (the page is now white).
5. Press F5.
6. Disable background-color: black on <body>.

What is the expected behavior?
The page is not white.

What went wrong?
The page stays black.

Did this work before? N/A 

Chrome version: 52.0.2743.116, 54.0.2832.0  Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2), canary and 
Flash Version: 

You can do the same with the other <div> (I suspected that it is an issue specific to <body>, but it is not).

Comment 1 by phistuck@chromium.org, Aug 18 2016

Components: -Platform>DevTools Platform>DevTools>HTML
Status: Untriaged (was: Unconfirmed)
Summary: Cannot disable dynamically added CSS declarations on a selected element across refreshes (was: Cannot disable dynamically added properties on a selected element across refreshes)
Workarounds -
1. Close and re-open the Developer Tools feature.
2. Select a different element, refresh the page and go back to the element for which you wanted to disable the CSS declaration.

Comment 2 by l...@chromium.org, Aug 19 2016

Cc: l...@chromium.org
Owner: lushnikov@chromium.org
Status: Assigned (was: Untriaged)
Thanks for the great repro phistuck@.

Comment 3 by dgozman@chromium.org, Oct 31

Status: Archived (was: Assigned)
Bulk closing low-priority issues with no activity. Please re-file and refer to the closed issue if it's essential to fix.
►

Sign in to add a comment