RESOLVED FIXED 202428
results.webkit.org: Standardize styles in the drawer
https://bugs.webkit.org/show_bug.cgi?id=202428
Summary results.webkit.org: Standardize styles in the drawer
Jonathan Bedard
Reported 2019-10-01 13:11:48 PDT
At the moment, we have a disparate collection of font sizes, weights and colors in the control drawer. We should standardize these.
Attachments
Patch (4.72 KB, patch)
2019-10-01 13:22 PDT, Jonathan Bedard
no flags
dark-mode-screenshot (103.56 KB, image/png)
2019-10-01 13:25 PDT, Jonathan Bedard
no flags
standard-screenshot (91.06 KB, image/png)
2019-10-01 13:25 PDT, Jonathan Bedard
no flags
Patch (6.84 KB, patch)
2019-10-01 14:48 PDT, Jonathan Bedard
no flags
Patch for landing (6.84 KB, patch)
2019-10-01 15:58 PDT, Jonathan Bedard
no flags
Jonathan Bedard
Comment 1 2019-10-01 13:22:57 PDT
Jonathan Bedard
Comment 2 2019-10-01 13:25:08 PDT
Created attachment 379940 [details] dark-mode-screenshot
Jonathan Bedard
Comment 3 2019-10-01 13:25:25 PDT
Created attachment 379941 [details] standard-screenshot
Zhifei Fang
Comment 4 2019-10-01 13:47:02 PDT
Comment on attachment 379939 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=379939&action=review > Tools/resultsdbpy/resultsdbpy/view/static/library/css/webkit.css:2279 > + font-color: var(--boldInverseColor); Since bold is control by font-weight, maybe we should call this inverseColor ? > Tools/resultsdbpy/resultsdbpy/view/static/library/css/webkit.css:2334 > + font-weight: calc(2.5 * var(--fontWeight)); We need overwrite the whole default user agent for input and select, better to have one extra section as: select, input { font-weight: var(--fontWeight) } Webkit have a default font-weight:400 for select and input, only bold those seems weird to me. You may need to add this after line 478 > Tools/resultsdbpy/resultsdbpy/view/static/library/css/webkit.css:2363 > + color: var(--boldInverseColor); if the input is disabled, it should have a different color. It should have a different color. Otherwise it will be hard for user to understand this input is disabled, you may need other --DisableInverseColor
Jonathan Bedard
Comment 5 2019-10-01 14:46:19 PDT
Comment on attachment 379939 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=379939&action=review >> Tools/resultsdbpy/resultsdbpy/view/static/library/css/webkit.css:2363 >> + color: var(--boldInverseColor); > > if the input is disabled, it should have a different color. It should have a different color. Otherwise it will be hard for user to understand this input is disabled, you may need other --DisableInverseColor We probably do want that long term, but for now, I'll just keep this the way it is.
Zhifei Fang
Comment 6 2019-10-01 14:47:38 PDT
Comment on attachment 379939 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=379939&action=review >>> Tools/resultsdbpy/resultsdbpy/view/static/library/css/webkit.css:2363 >>> + color: var(--boldInverseColor); >> >> if the input is disabled, it should have a different color. It should have a different color. Otherwise it will be hard for user to understand this input is disabled, you may need other --DisableInverseColor > > We probably do want that long term, but for now, I'll just keep this the way it is. it is better to do a inline style if you want to keep the way it is.
Jonathan Bedard
Comment 7 2019-10-01 14:48:49 PDT
Jonathan Bedard
Comment 8 2019-10-01 14:51:47 PDT
(In reply to Jonathan Bedard from comment #7) > Created attachment 379952 [details] > Patch Doesn't actually change the way the results database looks, so I didn't update the screenshots.
Jonathan Bedard
Comment 9 2019-10-01 15:10:16 PDT
(In reply to Zhifei Fang from comment #6) > Comment on attachment 379939 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=379939&action=review > > >>> Tools/resultsdbpy/resultsdbpy/view/static/library/css/webkit.css:2363 > >>> + color: var(--boldInverseColor); > >> > >> if the input is disabled, it should have a different color. It should have a different color. Otherwise it will be hard for user to understand this input is disabled, you may need other --DisableInverseColor > > > > We probably do want that long term, but for now, I'll just keep this the way it is. > > it is better to do a inline style if you want to keep the way it is. Not actually sure why I changed it...by 'keep the way it is', I mean keeping it var(--greyDarker), not keeping my change (since I realize that was a bit ambiguous)
Zhifei Fang
Comment 10 2019-10-01 15:15:45 PDT
unofficially r=me
Aakash Jain
Comment 11 2019-10-01 15:42:56 PDT
rs=me
Jonathan Bedard
Comment 12 2019-10-01 15:58:42 PDT
Created attachment 379963 [details] Patch for landing
WebKit Commit Bot
Comment 13 2019-10-01 16:46:09 PDT
Comment on attachment 379963 [details] Patch for landing Clearing flags on attachment: 379963 Committed r250587: <https://trac.webkit.org/changeset/250587>
WebKit Commit Bot
Comment 14 2019-10-01 16:46:10 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 15 2019-10-01 16:47:20 PDT
Note You need to log in before you can comment on or make changes to this bug.