Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(728)

Issue 1828493002: MD Settings: Fix side navigation bar background color for RTL. (Closed)

Created:
4 years, 9 months ago by dpapad
Modified:
4 years, 9 months ago
Reviewers:
dschuyler
CC:
arv+watch_chromium.org, chromium-reviews, dbeam+watch-settings_chromium.org, michaelpg+watch-md-settings_chromium.org, michaelpg+watch-md-ui_chromium.org, stevenjb+watch-md-settings_chromium.org
Base URL:
https://chromium.googlesource.com/chromium/src.git@master
Target Ref:
refs/pending/heads/master
Project:
chromium
Visibility:
Public.

Description

MD Settings: Fix side navigation bar background color for RTL. BUG=593989 Committed: https://crrev.com/d22fae34f47ce95aee43167fef1eb3f6cb231a0a Cr-Commit-Position: refs/heads/master@{#382698}

Patch Set 1 #

Total comments: 2
Unified diffs Side-by-side diffs Delta from patch set Stats (+4 lines, -0 lines) Patch
M chrome/browser/resources/settings/settings_ui/settings_ui.html View 1 chunk +4 lines, -0 lines 2 comments Download

Messages

Total messages: 14 (5 generated)
dpapad
Before/after http://imgur.com/a/NXqc3. @Dave: Do you know of an appropriate bug to attach to this CL? ...
4 years, 9 months ago (2016-03-22 20:58:14 UTC) #3
dschuyler
On 2016/03/22 20:58:14, dpapad wrote: > Before/after http://imgur.com/a/NXqc3. > > @Dave: Do you know of ...
4 years, 9 months ago (2016-03-22 21:05:50 UTC) #4
dpapad
On 2016/03/22 at 21:05:50, dschuyler wrote: > On 2016/03/22 20:58:14, dpapad wrote: > > Before/after ...
4 years, 9 months ago (2016-03-22 21:11:45 UTC) #6
dschuyler
lgtm
4 years, 9 months ago (2016-03-22 21:13:10 UTC) #7
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/1828493002/1 View timeline at https://chromium-cq-status.appspot.com/patch-timeline/1828493002/1
4 years, 9 months ago (2016-03-22 21:15:52 UTC) #9
commit-bot: I haz the power
Committed patchset #1 (id:1)
4 years, 9 months ago (2016-03-22 22:02:59 UTC) #10
commit-bot: I haz the power
Patchset 1 (id:??) landed as https://crrev.com/d22fae34f47ce95aee43167fef1eb3f6cb231a0a Cr-Commit-Position: refs/heads/master@{#382698}
4 years, 9 months ago (2016-03-22 22:05:25 UTC) #12
michaelpg
https://codereview.chromium.org/1828493002/diff/1/chrome/browser/resources/settings/settings_ui/settings_ui.html File chrome/browser/resources/settings/settings_ui/settings_ui.html (right): https://codereview.chromium.org/1828493002/diff/1/chrome/browser/resources/settings/settings_ui/settings_ui.html#newcode50 chrome/browser/resources/settings/settings_ui/settings_ui.html:50: background-color: var(--settings-background-color); it would be nice if we didn't ...
4 years, 9 months ago (2016-03-23 00:18:32 UTC) #13
dpapad
4 years, 9 months ago (2016-03-23 00:40:18 UTC) #14
Message was sent while issue was closed.
https://codereview.chromium.org/1828493002/diff/1/chrome/browser/resources/se...
File chrome/browser/resources/settings/settings_ui/settings_ui.html (right):

https://codereview.chromium.org/1828493002/diff/1/chrome/browser/resources/se...
chrome/browser/resources/settings/settings_ui/settings_ui.html:50:
background-color: var(--settings-background-color);
On 2016/03/23 at 00:18:32, michaelpg wrote:
> it would be nice if we didn't have to duplicate this
> 
> I guess we can't comma-separate the mixins like we can with toplevel CSS
rules, but wdyt about creating a separate common mixin to @apply in each of
these mixins?
> 
> or would that be terrible in itself?

I am not very familiar with CSS mixins. Can you use @apply within a mixin? Also,
if I understand your suggestion it would look something as follows,

--side-nav-background: {
  background-color: var(--settings-background-color);
}
--paper-drawer-panel-left-drawer-container: {
  @apply(--side-nav-background);
}
--paper-drawer-panel-right-drawer-container: {
  @apply(--side-nav-background);
}

So now instead of repeating the CSS variable twice, we have an extra level of
indirection, so we repeat the new mixin twice. Is that any better (or am I
misunderstanding the suggestion)?

Powered by Google App Engine
This is Rietveld 408576698