Revert "Reland [webauthn] Polish Touch ID UI" This reverts commit 5fcdfc79726d066c2088fe8158d44e832d57dd4d. Reason for revert: GPMPasskeysAuthenticatorDialogTest.InvokeUi_touchid fails Original change's description: > Reland [webauthn] Polish Touch ID UI > > This is a reland of crrev.com/c/5403928, with fixes for the broken > tests. There were some merge conflicts so it's a manual cherry pick, > hence the lack of integration with gerrit UI. > > Polish the Touch ID GPM UI: > * Move the UI to a sheet. > * Wait for the animation to finish before proceeding. > * Add text displaying the account details (for get assertion & make > credential) > * Catch Touch ID being locked and defer to a password if that happens. > * Remove old bubble code. > > Cq-Include-Trybots: luci.chromium.try:mac11-arm64-rel,mac10.15-blink-rel > Bug: 40274370 > Change-Id: If4b5d8cc57ec2c18def07c04c09ba0621412ca5d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5435978 > Auto-Submit: Nina Satragno <nsatragno@chromium.org> > Commit-Queue: Nina Satragno <nsatragno@chromium.org> > Commit-Queue: Ken Buchanan <kenrb@chromium.org> > Reviewed-by: Ken Buchanan <kenrb@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1284653} Bug: 40274370, 333610537 Change-Id: Ic345f28579ef9ce8b82eca34ec0fb77264a67a3c Cq-Include-Trybots: luci.chromium.try:mac11-arm64-rel,mac10.15-blink-rel Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5439040 Commit-Queue: Eugene Zemtsov <ezemtsov@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Eugene Zemtsov <ezemtsov@google.com> Cr-Commit-Position: refs/heads/main@{#1284829}
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.