Make ElementInternals setValidity use HTMLElement According to the HTML spec and the ElementInternals-validation WPT, we should be using HTMLElement instead of Element as the argument type in setValidity: https://html.spec.whatwg.org/multipage/custom-elements.html#the-elementinternals-interface Bug: 1420805 Change-Id: Ica7059c0a688a4290de18368828087199c74225a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4661473 Reviewed-by: David Baron <dbaron@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1164855}
ChromiumChromium 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.