Fire composition events if composition has been started and completed in same edit session.

Some IMEs may start and complete composition within same edit session.
Therefore, we should still fire composition events at the moment where
we commit the text to blink.

This change also contains several refactors:
1. Refactor code in |CommitTextAndEndCompositionIfAny|.

2. Moves logic to set |new_text_inserted_| from |TSFTextStore::SetText|
to |TSFTextStore::InsertTextAtSelection| since IMEs may directly invoke
the latter method. We need to correctly set the |new_text_inserted_|
flag in order to push text states to blink.

3. |TSFTextStore::InsertTextAtSelection| may be called several times in
single edit session. Therefore, we need to aggregate all replacement
ranges into single |replace_text_range_|.

4. In |TSFTextStore::RequestLock|, we should also reset all caches such
as |new_text_inserted_| even when the function early returns.

5. In |TSFTextStore::RequestLock|, use the replace text end pos instead
of the cached |composition_start_| as the |new_composition_start|.

Bug: 1099125
Change-Id: Ibfa2ff284a183939596d9ea2a5e7105e8139b099
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2274245
Reviewed-by: Yohei Yukawa <yukawa@chromium.org>
Reviewed-by: Siye Liu <siliu@microsoft.com>
Reviewed-by: Anupam Snigdha <snianu@microsoft.com>
Commit-Queue: Siye Liu <siliu@microsoft.com>
Commit-Queue: Anupam Snigdha <snianu@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#788799}
3 files changed
tree: 78c59c74715fc0a2514345f882e952391443f7bb
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. ENG_REVIEW_OWNERS
  68. LICENSE
  69. LICENSE.chromium_os
  70. OWNERS
  71. PRESUBMIT.py
  72. PRESUBMIT_test.py
  73. PRESUBMIT_test_mocks.py
  74. README.md
  75. WATCHLISTS
README.md

Logo Chromium

Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.

The project's web site is https://www.chromium.org.

Documentation in the source is rooted in docs/README.md.

Learn how to Get Around the Chromium Source Code Directory Structure .

For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.