Bug 154492

Summary: Web Inspector: Modifying CSS value in the styles sidebar stripped all CSS that followed that value
Product: WebKit Reporter: Nikita Vasilyev <nvasilyev>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: graouts, hi, inspector-bugzilla-changes, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
Attachments:
Description Flags
[Image] Bug
none
[Video] Screencast none

Nikita Vasilyev
Reported 2016-02-19 21:41:13 PST
Created attachment 271845 [details] [Image] Bug This bug happened to me once, but I can't reproduce it. I inspected the Inspector, and in "Styles - Rules" sidebar, I changed color value. Then I opened that modified CSS resource and everything after that color value was removed. See the attached screenshot. The rule that I changed was: .visual-style-property-container.comma-separated-keyword-editor > .visual-style-property-value-container > .visual-style-comma-separated-keyword-list > .visual-style-comma-separated-keyword-item > .titles > .subtitle
Attachments
[Image] Bug (209.02 KB, image/png)
2016-02-19 21:41 PST, Nikita Vasilyev
no flags
[Video] Screencast (1.41 MB, video/quicktime)
2018-06-01 19:39 PDT, Nikita Vasilyev
no flags
Radar WebKit Bug Importer
Comment 1 2016-02-19 21:41:25 PST
Nikita Vasilyev
Comment 2 2016-02-19 21:46:21 PST
No errors were thrown.
Nikita Vasilyev
Comment 3 2018-06-01 19:39:00 PDT
Created attachment 341818 [details] [Video] Screencast
Nikita Vasilyev
Comment 4 2018-06-01 19:39:10 PDT
Unmatched parenthesis cause this. Steps: 1. Open http://nv.github.io/webkit-inspector-bugs/154492_css-data-corruption/ 2. Inspect <body> 3. Click on "lightgoldenrodyellow" CSS value field 4. Type "rgb(1" 5. Press Tab Actual: All CSS properties and rules following the invalid value are gone. Expected: All CSS properties and rules following the invalid value stay unaffected.
Nikita Vasilyev
Comment 5 2019-02-10 20:23:03 PST
*** This bug has been marked as a duplicate of bug 182523 ***
Note You need to log in before you can comment on or make changes to this bug.