Feature request Command Line flag for location of Command Line flags configuration file
Reported by
illucent...@gmail.com,
Aug 4
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3507.0 Safari/537.36 Steps to reproduce the problem: 1. place chrome-flags.conf under $HOME/.config/ (or under $XDG_CONFIG_HOME) for google chrome 2. place chromium-flags.conf under $HOME/.config/ (or under $XDG_CONFIG_HOME) for chromium What is the expected behavior? Feature request. Making flags persistent. Specific flag for custom flags configuration file location, eg. --flags-config=<some location> What went wrong? $HOME/.config/chrom*-flags.conf file not readable Did this work before? No Does this work in other browsers? Yes Chrome version: 70.0.3507.0 Channel: dev OS Version: any / Fedora 27 (4.17.9-100.fc27.x86_64) Flash Version: - Thank You very much!
,
Aug 6
Thanks for filing the issue! As per comment#0 this seems to be a Feature request hence adding appropriate labels and marking it as Untriaged. Requesting someone from respective team to have a look into this.
,
Aug 7
,
Sep 9
|
||||
►
Sign in to add a comment |
||||
Comment 1 by vamshi.kommuri@chromium.org
, Aug 6