New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 3 users

Issue metadata

Status: WontFix
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on:
issue 616673
issue 671205

issue 653126
issue 674757

Sign in to add a comment

Issue 631270: Fix event dispatch to renderer in --use-mus-in-renderer

Reported by, Jul 25 2016 Project Member

Issue description

With --use-mus-in-renderer flag, chrome browser installs itself as the event handler for the chrome renderer ( As a result, events targeted to the renderer goes to RenderWidgetHostViewMus ( These events are currently dropped. We need to dispatch these events through RenderWidgetHostImpl/InputRouterImpl etc. to the renderer.

RenderWidgetHostViewAura knows how to dispatch ui::Events to the renderer. We should refactor that code, so that RenderWidgetHostViewMus can use the same code to dispatch the ui::Events it receives from the window server to the renderer.

Comment 1 by, Aug 4 2016

Blockedon: 616673

Comment 2 by, Oct 4 2016

Labels: Proj-Mustash

Comment 3 by, Oct 4 2016

Components: Internals>MUS

Comment 4 by, Oct 5 2016

Blocking: 653126

Comment 5 by, Oct 21 2016

Project Member
The following revision refers to this bug:

commit 2843ae3645cbbdf62b5ab7a16f89842ff40c86a2
Author: jonross <>
Date: Fri Oct 21 16:48:23 2016

We would like to share the event handling logic of RenderWidgetHostViewAura with RenderWidgetHostViewMus. As a first step this change refactors the EventHandler code out of RenderWidgetHostViewAura into its own class

TEST=manually run browser, dry-run of CQ to verify all existing tests.
BUG= 631270 

Cr-Commit-Position: refs/heads/master@{#426815}


Comment 6 by, Nov 29 2016

Project Member
The following revision refers to this bug:

commit d8cdf0429c899039b2b903888a680bce541c8cf4
Author: jonross <>
Date: Tue Nov 29 23:07:25 2016

Fix mus-in-renderer scale factor crash

Currently --mus-in-renderer crashes the renderer process on startup. The
WindowTreeClient attempts to check the display scale factor, but the screen
is not being set in that process.

This change returns a default scale factor when there is no available screen.
This will become redundant once aura-mus is ready, as proper screens will
be available.

TEST=manually ran --mus-in-renderer renderer works and paints.
BUG= 631270 

Cr-Commit-Position: refs/heads/master@{#435102}


Comment 7 by, Dec 5 2016

Blockedon: 671205

Comment 8 by, Dec 15 2016

Blocking: 674757

Comment 9 by, Jan 27 2017

Status: WontFix (was: Assigned)
This bug is invalid after the switch to the aura client-lib in the chrome-browser.

Comment 10 by, Feb 26 2018

Components: -Internals>MUS Internals>Services>WindowService

Comment 11 by, Feb 26 2018

Components: -MUS

Sign in to add a comment