mash: Support EventRewriterController and its rewriters.
These depend on an ash::Shell instance in Chrome.
Currently, they aren't created/initialized in Mash.
Event rewriters will need to live in the mus window server. kpschoedel@ and I have been discussing about this for a bit. (it's not clear yet who can work on this)
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
I'm coming up to speed here and hoping that I'll have a proposal soon.
dmazzoni@ had some good notes in related Issue 594887.
Issue 628665 and Issue 826529 are also somewhat related.
As far as I can tell, all the EventRewriters are hooked up okay for SingleProcessMash.
Unfortunately, the accessibility features using them seem to be blocked on Issue 888145.
Comment 1 by sadrul@chromium.org
, Sep 16 2016Labels: Proj-Mustash-Mus-WS
Owner: sadrul@chromium.org