Add README about prefs usage in ash |
||||
Issue descriptionAsh depends on //components/prefs and can use a PrefService* directly. It should do this instead of adding mojo methods to talk back to chrome to get pref data. There are some differences between classic ash and mash behavior (like the PrefService* can be null at startup while the connection is being established to the mojo pref service). Document this in a README, perhaps //ash/README.md
,
Sep 8 2017
,
Jan 22 2018
,
Jan 23 2018
,
Feb 26 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by jamescook@chromium.org
, Aug 7 2017