Chromium Code Reviews| Index: content/shell/android/javatests/src/org/chromium/content_shell_apk/ContentShellTestCommon.java |
| diff --git a/content/shell/android/javatests/src/org/chromium/content_shell_apk/ContentShellTestCommon.java b/content/shell/android/javatests/src/org/chromium/content_shell_apk/ContentShellTestCommon.java |
| index bda984042ad86895e6f2b6c56cda90e16604342f..78c146f72d2a88958c2b0da9ebb55d3b276d3346 100644 |
| --- a/content/shell/android/javatests/src/org/chromium/content_shell_apk/ContentShellTestCommon.java |
| +++ b/content/shell/android/javatests/src/org/chromium/content_shell_apk/ContentShellTestCommon.java |
| @@ -116,6 +116,13 @@ public final class ContentShellTestCommon { |
| }, WAIT_FOR_ACTIVE_SHELL_LOADING_TIMEOUT, CriteriaHelper.DEFAULT_POLLING_INTERVAL); |
| } |
| + void setCursorUpdateCallback(Runnable callback) { |
| + mCallback.getActivityForTestCommon() |
| + .getActiveShell() |
|
boliu
2017/05/31 16:30:03
activity accessors should happen on ui thread. use
jaebaek
2017/06/01 06:20:56
Ok, I will update it in that way, but have a quest
boliu
2017/06/01 16:14:50
they are probably also unsafe, in theory
|
| + .getViewAndroidDelegate() |
| + .setOnCursorUpdate(callback); |
| + } |
| + |
| ContentViewCore getContentViewCore() { |
| return mCallback.getActivityForTestCommon().getActiveShell().getContentViewCore(); |
| } |