WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED FIXED
194608
Web Inspector: CSS Changes: only show changes for the given node
https://bugs.webkit.org/show_bug.cgi?id=194608
Summary
Web Inspector: CSS Changes: only show changes for the given node
Devin Rousso
Reported
2019-02-13 13:29:16 PST
There should be a way to toggle between showing all changes for the entire page and only showing changes for the selected node.
Attachments
Patch
(6.45 KB, patch)
2019-03-03 20:56 PST
,
Devin Rousso
no flags
Details
Formatted Diff
Diff
[Image] Changes filter button - mockup
(205.26 KB, image/png)
2019-03-05 11:31 PST
,
Matt Baker
no flags
Details
Patch
(6.51 KB, patch)
2019-03-06 10:57 PST
,
Devin Rousso
no flags
Details
Formatted Diff
Diff
Show Obsolete
(1)
View All
Add attachment
proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1
2019-02-13 13:29:36 PST
<
rdar://problem/48050206
>
Devin Rousso
Comment 2
2019-03-03 20:56:23 PST
Created
attachment 363480
[details]
Patch
Matt Baker
Comment 3
2019-03-05 11:31:19 PST
Comment on
attachment 363480
[details]
Patch Being able to toggle this is great, but I think it needs to be more discoverable. What about a filter button? You'd have to place it in the header for the first file with changes, since there isn't a DetailsSection header.
Matt Baker
Comment 4
2019-03-05 11:31:51 PST
Created
attachment 363661
[details]
[Image] Changes filter button - mockup
Matt Baker
Comment 5
2019-03-05 11:32:33 PST
(In reply to Matt Baker from
comment #4
)
> Created
attachment 363661
[details]
> [Image] Changes filter button - mockup
It's not ideal placing the filter in the file header, since it appears that it applies just to that file. Maybe there is another approach we could take.
Timothy Hatcher
Comment 6
2019-03-06 10:47:12 PST
Comment on
attachment 363480
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=363480&action=review
> Source/WebInspectorUI/UserInterface/Views/SettingsTabContentView.js:220 > + generalSettingsView.addSetting(WI.UIString("CSS:"), WI.settings.cssChangesPerNode, WI.UIString("Show only for selected node"));
The user labels for this is not clear that this is about source changes.
Devin Rousso
Comment 7
2019-03-06 10:53:29 PST
Comment on
attachment 363480
[details]
Patch View in context:
https://bugs.webkit.org/attachment.cgi?id=363480&action=review
>> Source/WebInspectorUI/UserInterface/Views/SettingsTabContentView.js:220 >> + generalSettingsView.addSetting(WI.UIString("CSS:"), WI.settings.cssChangesPerNode, WI.UIString("Show only for selected node")); > > The user labels for this is not clear that this is about source changes.
🤦♂️ good point. I'll make the label "CSS Changes" instead.
Devin Rousso
Comment 8
2019-03-06 10:57:17 PST
Created
attachment 363760
[details]
Patch
Devin Rousso
Comment 9
2019-03-06 11:01:02 PST
(In reply to Matt Baker from
comment #3
)
> Being able to toggle this is great, but I think it needs to be more discoverable. What about a filter button? You'd have to place it in the header for the first file with changes, since there isn't a DetailsSection header.
(In reply to Matt Baker from
comment #5
)
> It's not ideal placing the filter in the file header, since it appears that it applies just to that file. Maybe there is another approach we could take.
For now, I'd like to get the basic functionality landed so I can actually make use of it. I've filed <
https://webkit.org/b/195365
> as a followup to create UI within the Changes panel for this.
Matt Baker
Comment 10
2019-03-06 11:06:00 PST
(In reply to Devin Rousso from
comment #9
)
> (In reply to Matt Baker from
comment #3
) > > Being able to toggle this is great, but I think it needs to be more discoverable. What about a filter button? You'd have to place it in the header for the first file with changes, since there isn't a DetailsSection header. > > (In reply to Matt Baker from
comment #5
) > > It's not ideal placing the filter in the file header, since it appears that it applies just to that file. Maybe there is another approach we could take. > > For now, I'd like to get the basic functionality landed so I can actually > make use of it. I've filed <
https://webkit.org/b/195365
> as a followup to > create UI within the Changes panel for this.
Sounds good. If we add an Export button we'll need a toolbar, so I'm sure there will be an opportunity to add a button for this somewhere.
WebKit Commit Bot
Comment 11
2019-03-06 11:22:36 PST
Comment on
attachment 363760
[details]
Patch Clearing flags on attachment: 363760 Committed
r242556
: <
https://trac.webkit.org/changeset/242556
>
WebKit Commit Bot
Comment 12
2019-03-06 11:22:37 PST
All reviewed patches have been landed. Closing bug.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug