New issue
Advanced search Search tips

Issue 756059 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocked on:
issue 869737
issue 738531

Blocking:
issue 678705



Sign in to add a comment

mash: Remove ash access from chrome/browser/chromeos/input_method

Project Member Reported by jamescook@chromium.org, Aug 16 2017

Issue description

Replace with mojo apis. See ash/README.md and go/mustash.

Some usage may be OK, since there's a different IME impl for mustash.

 
Blocking: 678705

Comment 2 by blakeo@chromium.org, Sep 27 2017

Owner: blakeo@chromium.org
Project Member

Comment 3 by bugdroid1@chromium.org, Oct 10 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f3d01a91059fc6ab782b149c840167f1fb2aef53

commit f3d01a91059fc6ab782b149c840167f1fb2aef53
Author: Blake O'Hare <blakeo@chromium.org>
Date: Tue Oct 10 05:02:48 2017

Remove unused #include's in input_method_manager_impl.cc

Which will also help remove some query noise while addressing
crbug.com/756059

Bug: 756059
Change-Id: Ib1ce004001d63f16540b9b5e4dfb6b5ad10c18fd
Reviewed-on: https://chromium-review.googlesource.com/700279
Reviewed-by: Shu Chen <shuchen@chromium.org>
Commit-Queue: Blake O'Hare <blakeo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#507592}
[modify] https://crrev.com/f3d01a91059fc6ab782b149c840167f1fb2aef53/chrome/browser/chromeos/input_method/input_method_manager_impl.cc

Comment 4 by blakeo@chromium.org, Dec 26 2017

Blockedon: 738531
Status: Assigned (was: Untriaged)
Some notes:

This is effectively a cover bug for 3 things that need to happen:

1) SendKeyEvent needs to be refactored in input_method_engine.cc

2) (mentioned in  crbug.com/738531 ) -> Move the CandidateWindow into Ash (used from candidate_window_controller_impl.cc) and then trigger via mojo call

3) (also mentioned in  crbug.com/738531 ) -> Similarly move the ModeIndicator into Ash used from mode_indicator_controller.cc

Components: -Internals>MUS Internals>Services>WindowService

Comment 6 by blakeo@chromium.org, Feb 27 2018

Owner: shend@chromium.org
Components: -Internals>Services>WindowService Internals>Services>Ash
Labels: -Proj-Mustash-Mash
Cc: shend@chromium.org
Owner: shuchen@chromium.org
Hi Shu, could you help triage? Thanks!
Re #4, I opened issue 869737 to track 2).

blakeo@, can you please elaborate more about 1)?
I don't quite understand why SendKeyEvent needs to be refactored.
Thanks!

Blockedon: 869737
Labels: Proj-Mustash
jamescook@: should ash access be removed in the tests under c/b/chromeos/input_method?

Labels: -Proj-Mustash Proj-Mash-SingleProcess
ash/public is the only thing non-ash code should depend upon.

There is some code that should be easily converted to work with single-process mash here. Specifically Shell::GetRootWindowForNewWindows can now use Screen::GetDisplayForNewWindows().
Project Member

Comment 18 by bugdroid1@chromium.org, Oct 22

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/5d7499de9212862a88b3c77212b420a1c48cfea0

commit 5d7499de9212862a88b3c77212b420a1c48cfea0
Author: Scott Violet <sky@chromium.org>
Date: Mon Oct 22 16:02:07 2018

chromeos: get CandidateWindowView to work for mash

The bubble implementation no longer needs the parent, instead it uses
Screen::GetDisplayForNewWindows(), which is what the code was using parent
for before.

BUG=756059
TEST=none

Change-Id: Ia58b6144cc6133027827f23ab240e094027c9a36
Reviewed-on: https://chromium-review.googlesource.com/c/1292513
Reviewed-by: Shu Chen <shuchen@chromium.org>
Commit-Queue: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#601596}
[modify] https://crrev.com/5d7499de9212862a88b3c77212b420a1c48cfea0/chrome/browser/chromeos/input_method/candidate_window_controller_impl.cc
[modify] https://crrev.com/5d7499de9212862a88b3c77212b420a1c48cfea0/chrome/browser/chromeos/input_method/textinput_test_helper.cc
[modify] https://crrev.com/5d7499de9212862a88b3c77212b420a1c48cfea0/ui/chromeos/ime/candidate_window_view.cc

Status: Fixed (was: Assigned)
The remaining includes of ash are only in classic mode, so they should be fine (they have been updated with mash-ok). I'm moving this to fixed.
Cc: steve...@chromium.org
Status: Assigned (was: Fixed)
We have one major usage that I am aware of in InputMethodManagerImpl::GetInputMethodKeyboardController().

keyboard::KeyboardController is part of ash. We need to replace calls to this to use ChromeKeyboardControllerClient::Get() instead.

Besides #20, the issue 869737 is still on going and blocking this issue.

Stephen, is InputMethodManagerImpl::GetInputMethodKeyboardController only an issue in multi-process?
Labels: -Proj-Mash-SingleProcess Proj-Mash-MultiProcess
Yes, that is correct, this now should only affect Multi-Process Mash. I'll change the label.

Sign in to add a comment