|
|
Chromium Code Reviews|
Created:
4 years ago by stevenjb Modified:
4 years ago CC:
chromium-reviews, michaelpg+watch-md-settings_chromium.org, michaelpg+watch-md-ui_chromium.org, dbeam+watch-settings_chromium.org, stevenjb+watch-md-settings_chromium.org, arv+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionMD Settings: About: Fixes to channel switcher dialog
BUG=666876
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
Committed: https://crrev.com/fa492598d6c2db6b6666e8f0f95c970d41c48e1c
Cr-Commit-Position: refs/heads/master@{#438038}
Patch Set 1 #
Total comments: 2
Messages
Total messages: 23 (10 generated)
Description was changed from ========== MD Settings: About: Fixes to channel switcher dialog BUG=666878 ========== to ========== MD Settings: About: Fixes to channel switcher dialog BUG=666878 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
stevenjb@chromium.org changed reviewers: + michaelpg@chromium.org
lgtm wrong CL bug #?
Description was changed from ========== MD Settings: About: Fixes to channel switcher dialog BUG=666878 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== MD Settings: About: Fixes to channel switcher dialog BUG=666876 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ==========
Oops, thanks, fixed.
The CQ bit was checked by stevenjb@chromium.org
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
Try jobs failed on following builders: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by stevenjb@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
CQ is committing da patch.
Bot data: {"patchset_id": 1, "attempt_start_ts": 1481594795987910, "parent_rev":
"5ccce0655ad535988ef198d8c4ef69fd04d927e0", "commit_rev":
"e625d5d127857c8474acc165d99a6b689e0f7965"}
Message was sent while issue was closed.
Description was changed from ========== MD Settings: About: Fixes to channel switcher dialog BUG=666876 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation ========== to ========== MD Settings: About: Fixes to channel switcher dialog BUG=666876 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2563143002 ==========
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== MD Settings: About: Fixes to channel switcher dialog BUG=666876 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Review-Url: https://codereview.chromium.org/2563143002 ========== to ========== MD Settings: About: Fixes to channel switcher dialog BUG=666876 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation Committed: https://crrev.com/fa492598d6c2db6b6666e8f0f95c970d41c48e1c Cr-Commit-Position: refs/heads/master@{#438038} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/fa492598d6c2db6b6666e8f0f95c970d41c48e1c Cr-Commit-Position: refs/heads/master@{#438038}
Message was sent while issue was closed.
dbeam@chromium.org changed reviewers: + dbeam@chromium.org
Message was sent while issue was closed.
https://codereview.chromium.org/2563143002/diff/1/chrome/browser/resources/se... File chrome/browser/resources/settings/about_page/channel_switcher_dialog.html (left): https://codereview.chromium.org/2563143002/diff/1/chrome/browser/resources/se... chrome/browser/resources/settings/about_page/channel_switcher_dialog.html:28: $i18n{aboutChannelDev} so wait... we want the new strings to differ from other parts of the code? settings.browserChannelToI18nId uses the old I18n keys: https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/about_... which is called by getUpdateStatusMessage_ https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/about_... do we want these UIs to match?
Message was sent while issue was closed.
https://codereview.chromium.org/2563143002/diff/1/chrome/browser/resources/se... File chrome/browser/resources/settings/about_page/channel_switcher_dialog.html (left): https://codereview.chromium.org/2563143002/diff/1/chrome/browser/resources/se... chrome/browser/resources/settings/about_page/channel_switcher_dialog.html:28: $i18n{aboutChannelDev} On 2016/12/14 03:41:02, Dan Beam wrote: > so wait... we want the new strings to differ from other parts of the code? > > settings.browserChannelToI18nId uses the old I18n keys: > https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/about_... > > which is called by getUpdateStatusMessage_ > https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/about_... > > do we want these UIs to match? Those strings are inserted into a sentence: https://cs.chromium.org/chromium/src/chrome/app/settings_strings.grdp?q=IDS_S... We were being a bit lazy here and just using the lower case "stable", etc in the dropdown also, instead of capitalized strings (with some extra text for dev): https://cs.chromium.org/chromium/src/chrome/app/settings_strings.grdp?q=IDS_S...
Message was sent while issue was closed.
On 2016/12/14 19:42:37, stevenjb wrote: > https://codereview.chromium.org/2563143002/diff/1/chrome/browser/resources/se... > File chrome/browser/resources/settings/about_page/channel_switcher_dialog.html > (left): > > https://codereview.chromium.org/2563143002/diff/1/chrome/browser/resources/se... > chrome/browser/resources/settings/about_page/channel_switcher_dialog.html:28: > $i18n{aboutChannelDev} > On 2016/12/14 03:41:02, Dan Beam wrote: > > so wait... we want the new strings to differ from other parts of the code? > > > > settings.browserChannelToI18nId uses the old I18n keys: > > > https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/about_... > > > > which is called by getUpdateStatusMessage_ > > > https://cs.chromium.org/chromium/src/chrome/browser/resources/settings/about_... > > > > do we want these UIs to match? > > Those strings are inserted into a sentence: > > https://cs.chromium.org/chromium/src/chrome/app/settings_strings.grdp?q=IDS_S... > > We were being a bit lazy here and just using the lower case "stable", etc in the > dropdown also, instead of capitalized strings (with some extra text for dev): > > https://cs.chromium.org/chromium/src/chrome/app/settings_strings.grdp?q=IDS_S... fwiw: material design has opinions about title case and use of punctuations, so what you may interpret as "lazy" may actually be desired by the spec https://material.google.com/style/writing.html#writing-capitalization-punctua...
Message was sent while issue was closed.
I'll double check with Alan about the capitalization. I interpreted the channel labels here (by themselves) as names. In any case, the context is different, which may affect localization (stand alone vs embedded in a sentence). On Dec 14, 2016 2:44 PM, <dbeam@chromium.org> wrote: > On 2016/12/14 19:42:37, stevenjb wrote: > > > https://codereview.chromium.org/2563143002/diff/1/chrome/ > browser/resources/settings/about_page/channel_switcher_dialog.html > > File chrome/browser/resources/settings/about_page/channel_ > switcher_dialog.html > > (left): > > > > > https://codereview.chromium.org/2563143002/diff/1/chrome/ > browser/resources/settings/about_page/channel_switcher_ > dialog.html#oldcode28 > > chrome/browser/resources/settings/about_page/channel_ > switcher_dialog.html:28: > > $i18n{aboutChannelDev} > > On 2016/12/14 03:41:02, Dan Beam wrote: > > > so wait... we want the new strings to differ from other parts of the > code? > > > > > > settings.browserChannelToI18nId uses the old I18n keys: > > > > > > https://cs.chromium.org/chromium/src/chrome/browser/ > resources/settings/about_page/about_page.js?q=browserChannelToI18nId&sq= > package:chromium&l=222&dr=C > > > > > > which is called by getUpdateStatusMessage_ > > > > > > https://cs.chromium.org/chromium/src/chrome/browser/ > resources/settings/about_page/about_page.html?q= > getUpdateStatusMessage_&sq=package:chromium&l=94&dr=C > > > > > > do we want these UIs to match? > > > > Those strings are inserted into a sentence: > > > > > https://cs.chromium.org/chromium/src/chrome/app/ > settings_strings.grdp?q=IDS_SETTINGS_UPGRADE_UPDATING_ > CHANNEL_SWITCH&sq=package:chromium&l=54&dr=C > > > > We were being a bit lazy here and just using the lower case "stable", > etc in > the > > dropdown also, instead of capitalized strings (with some extra text for > dev): > > > > > https://cs.chromium.org/chromium/src/chrome/app/ > settings_strings.grdp?q=IDS_SETTINGS_ABOUT_PAGE_DIALOG_ > CHANNEL_DEV&sq=package:chromium&dr=C&l=96 > > fwiw: material design has opinions about title case and use of > punctuations, so > what you may interpret as "lazy" may actually be desired by the spec > > https://material.google.com/style/writing.html#writing- > capitalization-punctuation > > https://codereview.chromium.org/2563143002/ > -- 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/12/14 22:50:58, stevenjb wrote: > I'll double check with Alan about the capitalization. I interpreted the > channel labels here (by themselves) as names. In any case, the context is > different, which may affect localization (stand alone vs embedded in a > sentence). > > > On Dec 14, 2016 2:44 PM, <mailto:dbeam@chromium.org> wrote: > > > On 2016/12/14 19:42:37, stevenjb wrote: > > > > > https://codereview.chromium.org/2563143002/diff/1/chrome/ > > browser/resources/settings/about_page/channel_switcher_dialog.html > > > File chrome/browser/resources/settings/about_page/channel_ > > switcher_dialog.html > > > (left): > > > > > > > > https://codereview.chromium.org/2563143002/diff/1/chrome/ > > browser/resources/settings/about_page/channel_switcher_ > > dialog.html#oldcode28 > > > chrome/browser/resources/settings/about_page/channel_ > > switcher_dialog.html:28: > > > $i18n{aboutChannelDev} > > > On 2016/12/14 03:41:02, Dan Beam wrote: > > > > so wait... we want the new strings to differ from other parts of the > > code? > > > > > > > > settings.browserChannelToI18nId uses the old I18n keys: > > > > > > > > > https://cs.chromium.org/chromium/src/chrome/browser/ > > resources/settings/about_page/about_page.js?q=browserChannelToI18nId&sq= > > package:chromium&l=222&dr=C > > > > > > > > which is called by getUpdateStatusMessage_ > > > > > > > > > https://cs.chromium.org/chromium/src/chrome/browser/ > > resources/settings/about_page/about_page.html?q= > > getUpdateStatusMessage_&sq=package:chromium&l=94&dr=C > > > > > > > > do we want these UIs to match? > > > > > > Those strings are inserted into a sentence: > > > > > > > > https://cs.chromium.org/chromium/src/chrome/app/ > > settings_strings.grdp?q=IDS_SETTINGS_UPGRADE_UPDATING_ > > CHANNEL_SWITCH&sq=package:chromium&l=54&dr=C > > > > > > We were being a bit lazy here and just using the lower case "stable", > > etc in > > the > > > dropdown also, instead of capitalized strings (with some extra text for > > dev): > > > > > > > > https://cs.chromium.org/chromium/src/chrome/app/ > > settings_strings.grdp?q=IDS_SETTINGS_ABOUT_PAGE_DIALOG_ > > CHANNEL_DEV&sq=package:chromium&dr=C&l=96 > > > > fwiw: material design has opinions about title case and use of > > punctuations, so > > what you may interpret as "lazy" may actually be desired by the spec > > > > https://material.google.com/style/writing.html#writing- > > capitalization-punctuation > > > > https://codereview.chromium.org/2563143002/ > > > > -- > 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 mailto:chromium-reviews+unsubscribe@chromium.org. Also, the spec says specifically: "Use sentence-style caps for all titles, headings, labels, menu items" So, it seems to me that the bug was correct and that these should be capitalized. That is also consistent with all of the Settings menus that I have tried. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
