Move Web Content to a sub-page |
||||||
Issue descriptionAs part of the merger of Appearance & Web Content, we added font-size, customize fonts, and page zoom to the top-level of the Appearance section. These settings used to be in Advanced settings, and were made more prominent as part of the move. We should evaluate whether they should stay at the top of Appearance or move to a Web Content sub-page. Justification for Pri-2: mocks were previously approved. We can track usage of these settings to see if moving them to a subpage is justified.
,
Apr 3 2017
,
Apr 3 2017
imo, the current UI with fonts and zoom shown at the top level in the Appearance section is an excellent choice. I'd vote to not change this UI at this time. Evaluating whether they should stay as they are: - Unless we re-add Web content in the advanced section, we will be deviating from the old options to some degree. - If we move [font size, customize fonts, page zoom] lines to a subpage we will only save two rows on the top level (i.e. we will still need a row to get to the new subpage). If we move them to a new top-level Web content section the options list will be larger. - Setting the font size seems less advanced than some other Appearance options such as "Use system title bar and borders", "Show bookmarks bar", and "Show home button"; i.e. if we are looking for opportunities to reduce the basic settings displayed, those seem like better choices to move elsewhere. If we decide to move them to a subpage: - we will need a row name for the subpage access. Web content doesn't convey Fonts and Zoom (maybe we could use "Fonts and Zoom"?).
,
Apr 3 2017
Alan, WDYT?
,
Apr 3 2017
This is a P2 so it's not needed for launch. That being said, changing your default font size/page zoom is something we don't expect many users to need versus people who want a home button or a bookmarks bar (which I also think is less complicated, given how font size / page zoom breaks some pages). "Web content" seems like a pretty reasonable name for the row since that's what the section title has been for a pretty long time.
,
Apr 7 2017
,
Apr 7 2017
This change seems pretty straightforward but might have some unforeseen consequences to it. Specifically around Customize fonts where the subpage would potentially become a sub-sub page...wither or not that's a good interaction is probably something that needs to be explored with updated mocks. "Web content" seems like an adequate level, but I think we can be more explicit or colloquial. Like "Webpage content" or "website content", per HC article: https://support.google.com/chrome/answer/114662?co=GENIE.Platform%3DDesktop&hl=en
,
Apr 9 2018
Clearing my ownership of P3 UI>Settings bugs. Feel free to re-assign once triaging is complete.
,
Oct 27
Closing this due to inactivity. I think a more general "reevaluate basic and advanced settings" effort is needed, especially in the context of ChromeOS where basic settings are now almost the same in size (if not larger) than "advanced". |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by tbuck...@chromium.org
, Mar 23 2017