Change and unify the splitter colors

NEW
Unassigned

Status

()

Firefox
Developer Tools
2 years ago
2 years ago

People

(Reporter: ntim, Unassigned)

Tracking

(Blocks: 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [polish-backlog][devtools-ux])

(Reporter)

Description

2 years ago
We currently have different splitter colors:
- #aaa (devtools light theme)
- #d0d0d0 (DevEdition light)
- #000 (Devtools dark theme)
- rgba(255,255,255,0.15) (Devtools tables - dark theme)
- rgba(0,0,0,0.15) (DevTools tables - light theme)

Older mockups by Stephen for reference: http://people.mozilla.org/~shorlander/mockups/devTools/ux-refresh-2013/
(Reporter)

Comment 1

2 years ago
Also, it would be nice to unify our "secondary" splitter colors (like the horizontal splitters that separate sections in the rules view, the font inspector or the style editor media sidebar).
(In reply to Tim Nguyen [:ntim] from comment #1)
> Also, it would be nice to unify our "secondary" splitter colors (like the
> horizontal splitters that separate sections in the rules view, the font
> inspector or the style editor media sidebar).

IIRC those are using --theme-splitter-color from https://developer.mozilla.org/en-US/docs/Tools/DevToolsColors (i.e. #aaa and #000).

I like the idea of lightening up the light theme one a bit (maybe to match the original mocks) and then also getting off of a full black on the dark theme.
Whiteboard: [devtools-ux]
(In reply to Brian Grinstead [:bgrins] from comment #2)
> I like the idea of lightening up the light theme one a bit (maybe to match
> the original mocks) and then also getting off of a full black on the dark
> theme.

Relevant: https://bugzilla.mozilla.org/show_bug.cgi?id=1205330
Also, for reference all the variables are defined in devtools/client/themes/variables.css (just moved them there in bug 1210954)
Depends on: 1210954
Whiteboard: [devtools-ux] → [polish-backlog][devtools-ux]
(Reporter)

Updated

2 years ago
Blocks: 1220368
You need to log in before you can comment on or make changes to this bug.