Bug 200761 - Web Inspector: Sources: enable by default
Summary: Web Inspector: Sources: enable by default
Status: RESOLVED DUPLICATE of bug 202341
Alias: None
Product: WebKit
Classification: Unclassified
Component: Web Inspector (show other bugs)
Version: WebKit Nightly Build
Hardware: All All
: P2 Normal
Assignee: Devin Rousso
Depends on:
Reported: 2019-08-14 23:44 PDT by Devin Rousso
Modified: 2019-10-07 16:41 PDT (History)
4 users (show)

See Also:

Patch (4.53 KB, patch)
2019-08-14 23:51 PDT, Devin Rousso
joepeck: review-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Devin Rousso 2019-08-14 23:44:06 PDT
I think that the Sources tab has reached a point where it's ready to be on-by-default.
Comment 1 Devin Rousso 2019-08-14 23:51:02 PDT
Created attachment 376363 [details]
Comment 2 Joseph Pecoraro 2019-08-16 01:04:32 PDT
Comment on attachment 376363 [details]

I suggest holding off on this a bit. Lets revisit this in a month.

I want to live on the Sources tab a bit more myself to ensure it feels good and to catch any possible issues. I suggest that others live on it and provide feedback here if they think something aught be addressed before it is enabled by default. I've only been living on it for about a week and have some thoughts.


I want to replace the default sources scope bar control to toggle between `Group by Path` / `Group by Type`. The current scope bar is a Resource Type filter, which should be with the other filters at the bottom. Burying the grouping toggles in the gear menu likely means they won't get noticed or used.

The existing filter buttons / controls don't make sense anymore. We should revamp that to make sense, especially in light of recent controls being added (bug 200425) in poor places because of the existing filter controls.

I want new icons, or at least an icon for origins in the "Group by Path" view (bug 200683).

In "Group by Path" I've had cases where deep nested folders gave a poor experience. That may just be a follow-up bug.

Finally, we have a few features in the pipeline (Bootstrap, Blackboxing) that are about to land. We should land those first and ensure they are at the quality bar we want before enabling the tab by default.
Comment 3 Devin Rousso 2019-10-07 16:41:12 PDT

*** This bug has been marked as a duplicate of bug 202341 ***