WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
RESOLVED DUPLICATE of
bug 201669
201039
Web Inspector: Changes CSS sidebar should not appear for selected Text node
https://bugs.webkit.org/show_bug.cgi?id=201039
Summary
Web Inspector: Changes CSS sidebar should not appear for selected Text node
Timothy Hatcher
Reported
2019-08-22 08:47:13 PDT
Created
attachment 377010
[details]
Screenshot See screenshot.
Attachments
Screenshot
(647.09 KB, image/png)
2019-08-22 08:47 PDT
,
Timothy Hatcher
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Devin Rousso
Comment 1
2019-08-22 09:27:32 PDT
This was the reason I filed <
https://webkit.org/b/194608
>.
Nikita Vasilyev
Comment 2
2019-08-22 10:33:24 PDT
I agree! (In reply to Devin Rousso from
comment #1
)
> This was the reason I filed <
https://webkit.org/b/194608
>.
I think we shouldn’t show Changes panel for Text nodes regardless of this setting.
Timothy Hatcher
Comment 3
2019-08-22 12:12:01 PDT
(In reply to Nikita Vasilyev from
comment #2
)
> I agree! > > (In reply to Devin Rousso from
comment #1
) > > This was the reason I filed <
https://webkit.org/b/194608
>. > > I think we shouldn’t show Changes panel for Text nodes regardless of this > setting.
I see, the setting fixes it. I agree, no reason to show for text nodes regardless.
Nikita Vasilyev
Comment 4
2019-09-12 12:27:04 PDT
*** This bug has been marked as a duplicate of
bug 201669
***
Nikita Vasilyev
Comment 5
2019-09-12 12:30:25 PDT
(In reply to Devin Rousso from
comment #1
)
> This was the reason I filed <
https://webkit.org/b/194608
>.
If that was the reason, can we remove the setting? We no longer show Changes panel for text nodes (regardless of the setting).
Devin Rousso
Comment 6
2019-09-12 15:22:34 PDT
(In reply to Nikita Vasilyev from
comment #5
)
> (In reply to Devin Rousso from
comment #1
) > > This was the reason I filed <
https://webkit.org/b/194608
>. > If that was the reason, can we remove the setting? We no longer show Changes panel for text nodes (regardless of the setting).
Sorry, I should've said "this was a reason". I still far prefer having the Changes panel be per-node. Frankly, I'd rather us have a Changes "view" in the Resources/Sources Tab (or even having our own Changes Tab). Having a details sidebar contain non-specific global state is very weird to me and doesn't fit our normal paradigm.
Timothy Hatcher
Comment 7
2019-09-12 19:29:27 PDT
(In reply to Devin Rousso from
comment #6
)
> (In reply to Nikita Vasilyev from
comment #5
) > > (In reply to Devin Rousso from
comment #1
) > > > This was the reason I filed <
https://webkit.org/b/194608
>. > > If that was the reason, can we remove the setting? We no longer show Changes panel for text nodes (regardless of the setting). > Sorry, I should've said "this was a reason". I still far prefer having the > Changes panel be per-node. Frankly, I'd rather us have a Changes "view" in > the Resources/Sources Tab (or even having our own Changes Tab). Having a > details sidebar contain non-specific global state is very weird to me and > doesn't fit our normal paradigm.
+1 to this.
Joseph Pecoraro
Comment 8
2019-09-13 00:15:06 PDT
> > Having a details sidebar contain non-specific global state is very weird to > > me and doesn't fit our normal paradigm. > > +1 to this.
+1. From me as well. Detail Sidebars provide additional data for something in the main content view. In the Element's tab it should be specific to the selected element. That said, I'd love to see a link from the Changes sidebar to a general "All Changes" ContentView which shows all Global changes. (Likely some other way to get there as well, but a quick link in the sidebar).
Nikita Vasilyev
Comment 9
2019-09-13 14:42:34 PDT
(In reply to Devin Rousso from
comment #6
)
> .. Frankly, I'd rather us have a Changes "view" in > the Resources/Sources Tab (or even having our own Changes Tab). Having a > details sidebar contain non-specific global state is very weird to me and > doesn't fit our normal paradigm.
I agree with you that having a details sidebar contain non-specific global is conceptually inconsistent. However, I'm not sold on the alternatives. This feature was made specifically for saving CSS changes made in the Styles panel. I added it as a panel to minimize context switching. Whatever we do, I'd like it to be: 1. Easy to discover after making changes in the Styles panel. 2. Access from Styles panel with one click. --- In the future, we may have more CSS/layout tools that are global (and not related to the selected DOM node). A few examples from other browsers: - Chrome DevTools have Animation panel that shows all animations on the page. It's at the bottom drawer (which we don't have). Their Changes view is there as well. It is hard to discover but it's easy to access. - Firefox DevTools have Fonts view that list all fonts used on the page. It's in the right sidebar of the Elements tab.
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