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

Issue 736325 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Oct 31
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Unable to edit css properties in Elements > Styles

Reported by tim.stcl...@gmail.com, Jun 23 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.109 Safari/537.36

Steps to reproduce the problem:
1. On a HTML5 page add an iframe which has a HTML5 document on it and references an external css file
2. Open the page, Inspect the content of the iframe
3. Modify a property of the css (e.g. div on the body)
4. Right-click the iframe, perform a "Reload Frame"
5. Go back to the property area: the property is now shown with a grey background (un-editable, similar to user agent stylesheet styles).
6. Shift-clicking a colour property still changes the colour format, but it remains un-editable

What is the expected behavior?
User-added CSS and properties should be editable at all times.

What went wrong?
Trying to modify properties using the css style editor in DevTools after a frame-based reload seems to be the only replicable path I can come up with. It seems to happen for properties that are internally defined by the user agent stylesheet (in my case figcaption and figure) as if the browser is seeing it as the user agent version and marking it as un-editable. The screenshot shows it editable to begin with, then after the iframe is reloaded the property becomes in-editable.

Did this work before? N/A 

Chrome version: 59.0.3071.109  Channel: stable
OS Version: OS X 10.12.5
Flash Version:
 
Screen Shot 2017-06-23 at 10.20.44 pm.png
68.7 KB View Download
Screen Shot 2017-06-23 at 10.25.06 pm.png
70.2 KB View Download

Comment 1 by hdodda@chromium.org, Jun 27 2017

Cc: hdodda@chromium.org
Labels: Needs-Feedback
@tim.stclair-- Could you please provide us the sample url/ test file to reproduce the issue and also help us by providing the screencast of the steps for better understanding.

Thanks!
Labels: Needs-Triage-M59
Cc: lushnikov@chromium.org
Owner: einbinder@chromium.org
Status: Assigned (was: Unconfirmed)
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