Revert "Dispatch input events after changing the element's selection" This reverts commit e8649745df235b61d061783dfb7af86ac0d130fe. Reason for revert: seems to cause test failure on linux-blink-web-tests-force-accessibility-rel. Original change's description: > Dispatch input events after changing the element's selection > > There was an old WebKit bug filed about this [1] that got resolved in > WebKit [2] but not in blink. > > The new proposed order simplifies Autofill's logic that now posts tasks > regarding input change events so that by the time they're processed the > selection would've been set properly. > > It also resolves flakiness of some PasswordManager test [3]. > > [1] https://bugs.webkit.org/show_bug.cgi?id=16976 > > [2] > https://sourcegraph.com/github.com/WebKit/WebKit@fecc89c90d3967bdf270e618601ca8b0d579ab0a/-/blob/Source/WebCore/editing/Editor.cpp?L1250-1263 > > [3] https://g-issues.chromium.org/issues/382342234#comment18 > > Bug: 394260849 > Change-Id: Id5acb4b4efd16cca52fad4daae0c8327d4f3dd74 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6198782 > Commit-Queue: Jihad Hanna <jihadghanna@google.com> > Reviewed-by: Siye Liu <siliu@microsoft.com> > Reviewed-by: Kent Tamura <tkent@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1419127} Bug: 394260849, 396056949 Change-Id: Ieccf822205ad79c3494d101b55fc69d77767ef5b No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6254538 Auto-Submit: Rushan Suleymanov <rushans@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Rushan Suleymanov <rushans@google.com> Cr-Commit-Position: refs/heads/main@{#1419176}
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.
If you found a bug, please file it at https://crbug.com/new.