Currently, Offline Pages live in 2 locations:
- component/offline_pages
- chrome/browser/android/offline_pages
The latter is needed to hook up the component to the UI and other browser-dependent things. Most of this code is not Android-specific and thus does nto have to live in c/b/a. Furthermore, over time it takes infusions of really Android-specific code which is bad, and it also prevents OfflinePages from being potentially implemented on other platforms.
In order to improve layering, the following can be done:
- create c/b/offline_pages
- move most of the code form c/b/a/o_p -> c/b/o_p, split Android-specific code into smaller platform parts.
- create c/b/offline_pages/android for those remaining android dependencies.
- [maybe] remove c/b/a/o_p
Comment 1 by chili@chromium.org
, May 15 2017