Feature Request: Provide 'More Info' URLs in chrome://flags
Reported by
tldr@fernandomiguel.net,
Apr 6 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.66 Safari/537.36 Steps to reproduce the problem: many of the flags and experiments in chrome://flags are really hard to decode or know what to expect for (power)users and people willing to participate in enabling them What is the expected behavior? Chrome should add a link for existing documentation for stable flags and for the desired outcome of experimental flags. What went wrong? N/A Did this work before? N/A Chrome version: 66.0.3359.66 Channel: beta OS Version: OS X 10.13.4 Flash Version:
,
Apr 8 2018
,
Apr 9 2018
Reporter@ Thanks for the issue. This is a feature request to provide more info URLs in chrome://flags. hence marking this as Untriaged for further updates from Dev. Thanks..
,
Apr 9 2018
Re #1, UI>Browser>WebUI is what I've used in the past. However there isn't an explicit chrome://flags owner. I think this could be resolved by the developer implementing a flag writing clearer descriptions within reason. Maintaining a separate doc would just be extra overhead which could easily get out of sync. Not all flags are intended for everyone to try and could cause Chrome to misbehave, crash or even lose data. So the general advice is not to turn on a flag if you don't understand what the flag setting is intended to do.
,
Apr 10 2018
Hi Edward, I was referring to cases where design docs exist, like this https://www.chromium.org/developers/design-documents/site-isolation where it directly relates to a few flags like chrome://flags/#enable-site-per-process bottom line, better descriptions surely help, and if there is an extended document, it should potentially be linked to, to help users, testers, and developers find the motivation.
,
Apr 10 2018
Thanks for the context. Agreed about adding appropriate links where available, but this would be on a flag by flag basis and shouldn't need a wholesale change to the flags template. I just did a quick test and it's possible to enter HTML links into the descriptions https://cs.chromium.org/chromium/src/chrome/browser/flag_descriptions.cc This probably just requires Chrome developer education.
,
Apr 10 2018
Perfect :) |
||||
►
Sign in to add a comment |
||||
Comment 1 by elawrence@chromium.org
, Apr 6 2018Components: Internals
Summary: Feature Request: Provide 'More Info' URLs in chrome://flags (was: provide a url link to chrome://flags experiemnts)