Including = in a css attribute locks it from being edited
Reported by
mohamed....@vidyard.com,
Jul 23
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Steps to reproduce the problem: 1. Browse to any page, open devtools 2. Add a new style attribute to any element, but include an "=" character in it. Also, add a value to the attribute. E.g. "background=color: none;" 3. Attribute cannot be altered, removed, or disabled. What is the expected behavior? Attribute should always allow its alteration, removal, or disabling. What went wrong? I discovered this error when I accidentally typed in "=" instead of "-" while entering a CSS attribute. Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: OS X 10.11.6 Flash Version:
,
Jul 24
Reporter@ - Thanks for filing the issue...!! Could you please provide a sample test file/url to test the issue from TE-end. This will help us in triaging the issue further. Thanks...!!
,
Jul 24
For sure - here's two screenshots of me visiting https://google.ca with devtools showing its initial state, and me adding a faulty CSS attribute to it.
,
Jul 24
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 26
Works for me on 67.0.3396.99. Would it be possible for you to provide a screencast?
,
Jul 30
Sure thing, here you go: https://share.vidyard.com/watch/26K35LJ8dxMNJjNUPUCRa3 I'm also on 67.0.3396.99, FWIW.
,
Jul 30
Just noticed that the cursor doesn't align with where I'm clicking in the screencast - sorry about that, that's just a recording issue so please ignore it.
,
Jul 30
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 30
Thanks for the screencast, now I can repro it!
,
Jul 30
No problem, glad to have cleared things up!
,
Dec 4
I can't repro this anymore on Chrome 70. Tentatively marking as fixed.
,
Dec 4
Seems like the issue is fixed for me as well (on 70.0.3538.110). |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by krajshree@chromium.org
, Jul 24