Revert "Mash - Support for browser themes in window frame."
This reverts commit 5d480c70. Reason for revert: Findit (https://goo.gl/kROfz5) identified CL at revision 556549 as the culprit for failures in the build cycles as shown on: https://findit-for-me.appspot.com/waterfall/culprit?key=ag9zfmZpbmRpdC1mb3ItbWVyRAsSDVdmU3VzcGVjdGVkQ0wiMWNocm9taXVtLzVkNDgwYzcwNDk5NGVhODJjNGYzY2ExZmQ5NGIxNzYxNjY4YzY4NDkM Sample Failed Build: https://ci.chromium.org/buildbot/chromium.chromiumos/linux-chromeos-dbg/5560 Sample Failed Step: browser_tests Original change's description: > Mash - Support for browser themes in window frame. > > 1. Move BrowserFrameHeaderAsh to //ash/frame and rename to > CustomFrameHeader. > 2. Use CustomFrameHeader for browser windows (in HeaderView). > Continue to use DefaultFrameHeader for other windows. > Possible TODO: share more code between the two FrameHeader classes. > 3. Transport frame images over mojo so Mash can apply them > via CustomFrameHeader. > > For now, only the active frame image is propagated (as a POC). > The inactive image, overlay images, and frame colors are TODO. > Ideally, there should be no behavioral changes in classic Ash. > > BUG=704942,836992 > > Change-Id: I15b2d357bd3c8b60b6656ebce910d476ce107b44 > Reviewed-on: https://chromium-review.googlesource.com/1043221 > Reviewed-by: Tom Sepez <tsepez@chromium.org> > Reviewed-by: Scott Violet <sky@chromium.org> > Commit-Queue: Evan Stade <estade@chromium.org> > Cr-Commit-Position: refs/heads/master@{#556549} No-Presubmit: true No-Tree-Checks: true No-Try: true BUG=704942,836992 Change-Id: Ibe6fc13c61d33eac241fed00edb194cc248429de Reviewed-on: https://chromium-review.googlesource.com/1049145 Cr-Commit-Position: refs/heads/master@{#556631}
Showing
This diff is collapsed.
Please register or sign in to comment