Entering a css property for given element in a form of value:key makes it frozen
Reported by
przemek....@gmail.com,
Oct 4
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. Open devtools, try to update css rules for given element 2. As a property name, use "1px solid #e6e6e6" 3. Go to start of the input, add border: 4. As you see, given property (or section) gets frozen - it doesn't disappear or behaves in an uncommon way What is the expected behavior? IMO it would be nice to let us write rules in a given order [value] then add key at the beginning: [key:value] What went wrong? Starting from value makes given property unusable. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: OS X 10.14.0 Flash Version:
,
Oct 5
The behavior is currently as intended, expecting the key to be typed first. Agree it might be nice to smartly detect if the user typed a value first instead, rather than a key. Realistically, it's probably not high enough priority for us to get around to changing the behavior though, unless enough others agree. |
||
►
Sign in to add a comment |
||
Comment 1 by swarnasree.mukkala@chromium.org
, Oct 5