New issue
Advanced search Search tips

Issue 750963 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 753012



Sign in to add a comment

Add README about prefs usage in ash

Project Member Reported by jamescook@chromium.org, Aug 1 2017

Issue description

Ash 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

 
Blocking: 753012
Status: Fixed (was: Assigned)
Added to //ash/README.md in 6350adcc5083ca5fbc086e438c192362f6dcf1d6

Comment 3 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Comment 4 by dchan@chromium.org, Jan 23 2018

Status: Fixed (was: Archived)
Components: -Internals>MUS Internals>Services>WindowService

Sign in to add a comment