Revert "Fix delegated ink trails in OOPIF"

This reverts commit b8c06872c6cfa5a1be26bd0f801aa1f350538fd7.

Reason for revert: crbug.com/1215704 

Original change's description:
> Fix delegated ink trails in OOPIF
>
> Today, delegated ink trails do not work in OOPIFs. The
> RenderFrameMetadata with the delegated ink flag set on it arrives in a
> provider held by RenderWidgetHostImpl that is associated with the OOPIF.
> This makes sense, but the issue is that the OOPIF's view is a
> RenderWidgetHostViewChildFrame, which does not hold an EventHandler.
> Then, when future pointerevents arrive in the browser, they are not
> checking the correct widget for a delegated ink flag. Therefore, points
> are not being forwarded for delegated ink trails.
>
> This fix moves the place that we decide to forward delegated ink points
> into the RenderWidgetHostInputEventRouter, which is slightly later in
> the execution. By doing this, hit testing will have occurred and we
> will have the RenderWidgetHostViewChildFrame as the target, allowing us
> to directly query that view's widget for a delegated ink flag. Then
> forwarding will work as it did from RenderWidgetHostViewEventHandler.
>
> Bug: 1052145
> Change-Id: I0b22b98ae73be97217c0b45cf2e5c3e6a4e32577
> Cq-Do-Not-Cancel-Tryjobs: true
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2857102
> Reviewed-by: Ken Buchanan <kenrb@chromium.org>
> Reviewed-by: Jonathan Ross <jonross@chromium.org>
> Reviewed-by: Scott Violet <sky@chromium.org>
> Reviewed-by: Daniel Libby <dlibby@microsoft.com>
> Commit-Queue: Mario Bianucci <mabian@microsoft.com>
> Cr-Commit-Position: refs/heads/master@{#888498}

Bug: 1052145, 1215704
Change-Id: I501df4b3fe9736cbed5d677ae72906cb331bb347
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2935138
Auto-Submit: François Doray <fdoray@chromium.org>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: François Doray <fdoray@chromium.org>
Owners-Override: François Doray <fdoray@chromium.org>
Cr-Commit-Position: refs/heads/master@{#888609}
16 files changed
tree: 5547df786a574064d1d529cb3175fc0323e1f0f3
  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. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.

To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.

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.