Closed Bug 1507367 Opened 7 years ago Closed 7 years ago

Clean up components in DevTools

Categories

(bugzilla.mozilla.org :: Administration, task)

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Staging
Type:
task
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: emceeaich, Unassigned)

References

(Blocks 1 open bug)

Details

Components in DevTools can be merged and cleaned up.
Flags: needinfo?(past)
I've looked at the components and I have changed my mind on this. My initial thinking was that we should merge the inspector components (Inspector, Font Inspector, DOM, Computed Styles Inspector, CSS Rules Inspector) and the shared components (Shared Components, Source Editor, Object Inspector).However I believe that the teams are using multiple components to facilitate a simpler triage process and this is something I believe we should encourage. At the very least, merging is a request that should appear bottom-up, rather than top-down. There are 3 components that will be retired soon, Canvas Debugger, Web Audio Editor and WebGL Shader Editor, so we can use this bug to track their eventual move to the graveyard. Layout Frame Inspector is one component that seems to have been created too hastily, but I'll let Patrick deal with that as he sees fit.
Flags: needinfo?(past)
(In reply to Panos Astithas (he/him) [:past] (please ni?) from comment #1) > My initial thinking was that we should merge the inspector components (Inspector, Font > Inspector, DOM, Computed Styles Inspector, CSS Rules Inspector) [...] > However I believe that the teams are using multiple components to > facilitate a simpler triage process and this is something I believe we > should encourage. At the very least, merging is a request that should appear > bottom-up, rather than top-down. Absolutely agree on this. I'm leading the inspector team now, and we were the ones asking for many components to be created (font, computed style, rules, ...) and we are thinking of asking for even more. It's been useful to us in the past to categorize bugs about different tools. Indeed, the inspector is such a big tool that there are very different areas in there and we need ways to categorize bugs belonging to these different areas. Maybe we're mis-using the system though. Maybe components should be simpler/fewer so users can easily file bugs, and instead we should use whiteboard flags or something else.
If components help you, then you should use them. We can work around the UX for filing bugs to make them end up in the right place.
I'm going to close this as wontfix and we can revisit in future bugs.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
(In reply to Panos Astithas (he/him) [:past] (please ni?) from comment #1) > Layout Frame Inspector is one component that > seems to have been created too hastily, but I'll let Patrick deal with that > as he sees fit. I meant to comment on this point earlier but forgot to. Yes, Panos is correct here, this component was created a little bit too fast at a time when we thought we'd be working on a new tool, but we ended up not because of a change of plan. So we should remove this component. I'll look at bugs in there and close/move them if needed, and I'll file an admin bug to remove the component.
You need to log in before you can comment on or make changes to this bug.