Content Modularization Project: Provide means for client to obtain time info independent of //content |
||||||||
Issue descriptionAs part of enabling time zone monitoring to be used as a service independent of //content, we need to generalize the mechanisms that //content/renderer uses to read time zone info. The issues involved in doing this are non-trivial. The issues and tentative plan for tackling them are described here: https://docs.google.com/document/d/1ukMujoNM9eK7eTXlMfSzHp-ydep5xpVHrkhHBeE9ADQ/edit#heading=h.8h599u668pfy
,
Feb 2 2017
Note that the design for this is in flux due to potentially changing renderer-side requirements; see the comments by jshin@ on the design doc linked above. The first step is thus to resolve the relationship of those comments to the work here.
,
Mar 24 2017
Hi, I'm curious about this issue,, does this relate with our Device Service development? Thanks.
,
Mar 24 2017
Yes, indeed. However, we haven't yet nailed down how to tackle it (look through the design doc if curious).
,
Mar 25 2017
OK, I see, this does not block servicification work itself but is to enable time_zone_monitor clients to work well even outside of //content context.
,
Mar 27 2017
Correct!
,
Nov 7 2017
,
Nov 7 2017
Migrating S13N meta bugs to Type=Task, so that they can be distinguished from technical work.
,
Nov 8 2017
,
Nov 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by blundell@chromium.org
, Jan 26 2017