Content Modularization Project: Navigation |
||||||||
Issue descriptionExtract the frame server/navigation code from //content into //services/navigation. This code should: - not know about specific WP features (requests for interfaces unrelated to navigation should be delegated to its client) - not know too much about UI (instead, this should be left to Mus, though individual navigable views/frames should have mus::Windows).
,
Oct 13 2017
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 13 2017
We're planning to do this, though we likely won't have time to get started until next quarter. This will be easiest once the old non-PlzNavigate code is deleted, so this is kind of blocked on issue 689549. (PlzNav is enabled on M61 for everywhere but Android Webview, and I think that's targeted for M63?)
,
Oct 13 2017
,
Oct 23 2017
,
Oct 23 2017
,
Nov 3 2017
,
Nov 7 2017
Appending component Internals>Services to S13N projects and changing the Type (for tracking sake) to Type=Task. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by creis@chromium.org
, Oct 12 2016Components: UI>Browser>Navigation