|
|
Created:
4 years, 2 months ago by Dan Beam Modified:
4 years, 2 months ago 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 Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMD Settings: preload Roboto bold to reduce flicker
R=dpapad@chromium.org
BUG=651730
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
Committed: https://crrev.com/90bc6bfd63b17209926b0028f34ef8cd3e36b620
Cr-Commit-Position: refs/heads/master@{#422514}
Patch Set 1 : @override #
Total comments: 2
Patch Set 2 : comment for dpapad@ #Messages
Total messages: 20 (11 generated)
Description was changed from ========== MD Settings: preload Roboto bold to reduce flicker R=dpapad@chromium.org BUG=651730 ========== to ========== MD Settings: preload Roboto bold to reduce flicker R=dpapad@chromium.org BUG=651730 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
The CQ bit was checked by dbeam@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was checked by dbeam@chromium.org to run a CQ dry run
Patchset #1 (id:1) has been deleted
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: This issue passed the CQ dry run.
LGTM https://codereview.chromium.org/2385873002/diff/20001/chrome/browser/resource... File chrome/browser/resources/settings/settings_ui/settings_ui.js (right): https://codereview.chromium.org/2385873002/diff/20001/chrome/browser/resource... chrome/browser/resources/settings/settings_ui/settings_ui.js:110: document.fonts.load('bold 12px Roboto'); Perhaps add a short comment explaining why this is necessary. I don't think it will be obvious to future readers.
https://codereview.chromium.org/2385873002/diff/20001/chrome/browser/resource... File chrome/browser/resources/settings/settings_ui/settings_ui.js (right): https://codereview.chromium.org/2385873002/diff/20001/chrome/browser/resource... chrome/browser/resources/settings/settings_ui/settings_ui.js:110: document.fonts.load('bold 12px Roboto'); On 2016/10/03 17:31:59, dpapad wrote: > Perhaps add a short comment explaining why this is necessary. I don't think it > will be obvious to future readers. Done.
The CQ bit was checked by dbeam@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from dpapad@chromium.org Link to the patchset: https://codereview.chromium.org/2385873002/#ps40001 (title: "comment for dpapad@")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #2 (id:40001)
Message was sent while issue was closed.
Description was changed from ========== MD Settings: preload Roboto bold to reduce flicker R=dpapad@chromium.org BUG=651730 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== MD Settings: preload Roboto bold to reduce flicker R=dpapad@chromium.org BUG=651730 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Committed: https://crrev.com/90bc6bfd63b17209926b0028f34ef8cd3e36b620 Cr-Commit-Position: refs/heads/master@{#422514} ==========
Message was sent while issue was closed.
Patchset 2 (id:??) landed as https://crrev.com/90bc6bfd63b17209926b0028f34ef8cd3e36b620 Cr-Commit-Position: refs/heads/master@{#422514}
Message was sent while issue was closed.
did we give up on `font-display`? On Mon, Oct 3, 2016, 1:31 PM commit-bot@chromium.org via codereview.chromium.org <reply@chromiumcodereview-hr.appspotmail.com> wrote: Patchset 2 (id:??) landed as https://crrev.com/90bc6bfd63b17209926b0028f34ef8cd3e36b620 Cr-Commit-Position: refs/heads/master@{#422514} https://codereview.chromium.org/2385873002/ -- You received this message because you are subscribed to the Google Groups "Chromium-reviews" group. To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
Message was sent while issue was closed.
On 2016/10/04 04:37:49, michaelpg wrote: > did we give up on `font-display`? I'm not sure but we had a big talk about whether we wanted to lazy/remotely load Roboto from the web fonts API. It'd save a bit of space for the installer, but it'd be slightly more code/access. Just don't think it was a huge priority for anybody yet, and font-display wasn't quite tune-able to our liking.
Message was sent while issue was closed.
On 2016/10/04 04:45:21, Dan Beam wrote: > On 2016/10/04 04:37:49, michaelpg wrote: > > did we give up on `font-display`? > > I'm not sure but we had a big talk about whether we wanted to lazy/remotely load > Roboto from the web fonts API. > > It'd save a bit of space for the installer, but it'd be slightly more > code/access. > > Just don't think it was a huge priority for anybody yet, and font-display wasn't > quite tune-able to our liking. ah ok, thanks for the context! |