Bug 150357

Summary: Web Inspector: Editing CSS via Styles sidebar doesn't update inline CSS in resources
Product: WebKit Reporter: Nikita Vasilyev <nvasilyev>
Component: Web InspectorAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: graouts, hi, inspector-bugzilla-changes, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: All   
OS: All   
See Also: https://bugs.webkit.org/show_bug.cgi?id=150298
Attachments:
Description Flags
[Animated GIF] Bug
none
[HTML] Reduction none

Nikita Vasilyev
Reported 2015-10-19 23:46:01 PDT
Created attachment 263555 [details] [Animated GIF] Bug See the attached GIF. Steps: 1. Open attached inline-styles.html 2. Inspect div.internal 3. Change background-color to "plum" 4. Inspect div[style] 5. Change background-color to "plum" 6. Open Resources tab Expected: Color values should be updated, e.g. be "plum". Actual: Color values didn't get updated, e.g. they are still "dodgerblue".
Attachments
[Animated GIF] Bug (658.73 KB, image/gif)
2015-10-19 23:46 PDT, Nikita Vasilyev 		no flags
Details
[HTML] Reduction (231 bytes, text/html)
2015-10-19 23:46 PDT, Nikita Vasilyev 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2015-10-19 23:46:24 PDT
<rdar://problem/23179548>
Nikita Vasilyev
Comment 2 2015-10-19 23:46:35 PDT
Created attachment 263556 [details] [HTML] Reduction
Joseph Pecoraro
Comment 3 2015-10-20 10:54:14 PDT
This is actually expected behavior right now. If I wanted to see the main resource's content, I would want to see the content that was sent over the wire, not modified content. However you could argue this is not what we do with stylesheets so we should be consistent. Seems a path forward would be the ability to show a resource with edits and without edits.
Devin Rousso
Comment 4 2015-10-20 16:45:30 PDT
(In reply to comment #3) > This is actually expected behavior right now. If I wanted to see the main > resource's content, I would want to see the content that was sent over the > wire, not modified content. However you could argue this is not what we do > with stylesheets so we should be consistent. Seems a path forward would be > the ability to show a resource with edits and without edits. I would actually expect the latter (updating the resource). Maybe add a button to toggle the resource between original and current (this could then be expanded into a diff tool)?
Timothy Hatcher
Comment 5 2015-10-21 17:11:58 PDT
(In reply to comment #4) > (In reply to comment #3) > > This is actually expected behavior right now. If I wanted to see the main > > resource's content, I would want to see the content that was sent over the > > wire, not modified content. However you could argue this is not what we do > > with stylesheets so we should be consistent. Seems a path forward would be > > the ability to show a resource with edits and without edits. > > I would actually expect the latter (updating the resource). Maybe add a > button to toggle the resource between original and current (this could then > be expanded into a diff tool)? We have both the original and current changes on SourceCode. get originalRevision() get currentRevision() We also have scaffolding for branches with Branch and BranchManager.
Note You need to log in before you can comment on or make changes to this bug.