commit | 6870b64e8c6eaa1493e6fc5a208dbb51305aaebc | [log] [tgz] |
---|---|---|
author | Ernesto Izquierdo Clua <eic@google.com> | Tue Oct 08 15:28:55 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 08 15:28:55 2024 |
tree | 7140760420ff6dce016ac6c69d05b0ac7aeebcd6 | |
parent | 0938a428053abe47169e333712999b11a9f3db82 [diff] |
[auto-iso] Create AutofillFormFeaturesJavaScriptFeature context: go/autofill-isolated-content-world This patch is part of a chain of changes needed to detect form submissions triggered by page scripts. Detecting submissions in the page content world requires some util functions to be injected in that world. Those functions are used to extract the form data that gets sent to the browser process. My initial approach was to create a separate javascript feature for injecting the utils in both worlds. This turned out to be overly complicated as there were many utils functions to inject. I switched my approach to instead inject FormUtilsJavaScriptFeature into both worlds. FormUtilsJavaScriptFeature injects form and fill util functions, but also a script to set feature flags in the renderer. The feature flags do not need to be in the page world, so I am creating in this patch a separate JavaScriptFeature to inject them in the isolated world. If in the future we need feature flags in the page world we can create a js feature for the page world. Change-Id: I3aaedcdd141a756e70505f9ecc74ab6d399c8a19 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5912776 Reviewed-by: Vincent Boisselle <vincb@google.com> Commit-Queue: Ernesto Izquierdo Clua <eic@google.com> Cr-Commit-Position: refs/heads/main@{#1365566}
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.