Make --use-mus-in-renderer the default for --mash |
|||||
Issue descriptionWhen chrome runs in --mash, the renderer should default to run as a mus-client. This bug tracks making that default mode, and removing the code no longer needed when it's the only option for --mash.
,
Feb 6 2017
Can we close this now?
,
Feb 6 2017
I am using this to track removal of unnecessary code too (see op)
,
Feb 6 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/be523b7cc0438b8bb9629c5863e1959a1e9fa272 commit be523b7cc0438b8bb9629c5863e1959a1e9fa272 Author: sadrul <sadrul@chromium.org> Date: Mon Feb 06 19:35:24 2017 mus: Fix creating the factory for window-tree-client in renderer. When a new tab is created, the browser first sends the request for the window tree client to be created, and then requests the creation of a RenderWidget. However, the renderer can also create a RenderWidget and notify the browser, which then asks for the window tree client to be created. So allow the window tree client to be created correctly for a RenderWidget in both of these cases. TBR=jam@ render_widget.cc since trivial rename of a function BUG= 686235 Review-Url: https://codereview.chromium.org/2676553003 Cr-Commit-Position: refs/heads/master@{#448351} [modify] https://crrev.com/be523b7cc0438b8bb9629c5863e1959a1e9fa272/content/renderer/mus/render_widget_window_tree_client_factory.cc [modify] https://crrev.com/be523b7cc0438b8bb9629c5863e1959a1e9fa272/content/renderer/mus/renderer_window_tree_client.cc [modify] https://crrev.com/be523b7cc0438b8bb9629c5863e1959a1e9fa272/content/renderer/mus/renderer_window_tree_client.h [modify] https://crrev.com/be523b7cc0438b8bb9629c5863e1959a1e9fa272/content/renderer/render_widget.cc
,
May 3 2017
,
Aug 1 2017
,
Jan 22 2018
,
Feb 26 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by bugdroid1@chromium.org
, Jan 31 2017