Add toolbar buttons to markup view

NEW
Unassigned

Status

()

Firefox
Developer Tools: Inspector
P3
enhancement
3 years ago
2 years ago

People

(Reporter: ntim, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [btpp-backlog])

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8645216 [details]
Chrome's toolbar screenshot

Chrome Canary has a quick access toolbar next to the inspector breadcrumbs (with the Material Design experiment enabled).
Provides handy options such as :
- Hide/Unhide element that toggles visibility: hidden on an element
- Edit as HTML
- Toggle HTML-related breakpoints
- Lock pseudo-classes
- A performance highlighter menu as well (not sure if this even makes sense in the markup view, but I guess they needed to put this somewhere)
Seems pretty cool and could be a nice way to surface the 'rulers' feature, among others (rather than it being a hidden feature).  As far as real-estate, maybe the search box could be hidden by default and then the left-most button could be 'search' which would show it (it would also become active and focused when pressing ctrl+f)
(In reply to Brian Grinstead [:bgrins] from comment #1)
> Seems pretty cool and could be a nice way to surface the 'rulers' feature,
> among others (rather than it being a hidden feature).  As far as
> real-estate, maybe the search box could be hidden by default and then the
> left-most button could be 'search' which would show it (it would also become
> active and focused when pressing ctrl+f)

I think this works for inspector-specific features. Does that include rulers? They seem tied to RDV as well.

Note for later: when the UX hire starts we should put this as part of a toolbox UX review:
* what tools should be top-level in the toolbox and on by default
* similarly, which top-level tools can be hidden by default
* what tools should instead be exposed via specific tools, eg design-oriented tools.
(In reply to Jeff Griffiths (:canuckistani) from comment #2)
> Note for later: when the UX hire starts we should put this as part of a
> toolbox UX review:
> * what tools should be top-level in the toolbox and on by default
> * similarly, which top-level tools can be hidden by default
> * what tools should instead be exposed via specific tools, eg
> design-oriented tools.
Definitely want to be part of this discussion. Very interesting.

A markup-view toolbar could also be a good way to surface to hidden-for-a-long-time Geometry Editor thing which, in time, I intend to turn into a tool to edit elements' size and position in content.
Inspector bug triage (filter on CLIMBING SHOES).
Severity: normal → enhancement
Priority: -- → P3
Whiteboard: [btpp-backlog]
You need to log in before you can comment on or make changes to this bug.