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

Issue 710889 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Aug 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 666958



Sign in to add a comment

Allow input on non-chromeos chrome/mus builds.

Project Member Reported by toniki...@chromium.org, Apr 12 2017

Issue description

Curreny Mus/IME implementation is chromeos oriented today. In order to allow very minimal keyboard input on non-chromeos/mus, I basically extended SimpleInputMethod like in [2], but this is not ideal.

[1] https://github.com/Igalia/chromium/commits/ozone-wayland-dev
[2] https://cs.chromium.org/chromium/src/chrome/browser/ui/views/ime_driver/simple_input_method.h?type=cs&q=simpleinputmethod&l=14

On a first thought, a action plan to fix this could be:

- remove the _chromeos suffix from input_method_bridge_chromeos.cc/h - hence, rename it to input_method_bridge.cc/h or alike.

- rename InputMethodBridge::input_method_chromeos_ to rename InputMethodBridge::input_method_.

- for ChromeOS initialize InputMethodBridge::input_method_ with InputMethodChromeOS.
  For linux, initialize it with InputMethodLinuxAura.

- Change InputMethodLinuxAura to work with Mus.

moshayedi@: wdyt?
 
Cc: sadrul@chromium.org sky@chromium.org
Components: -MUS Internals>Services>WindowService
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Status: WontFix (was: Assigned)
we moved away from mus for ozone/x11 and wayland on Linux builds. Thus, a new bug is required.

Sign in to add a comment