commit | 45b258ef29083938d08841b64b5514f27bf94bac | [log] [tgz] |
---|---|---|
author | David Song <wintermelons@google.com> | Tue Oct 26 23:24:52 2021 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Oct 26 23:24:52 2021 |
tree | f7b9b284e350bf234b6376a0bed365da44767502 | |
parent | b3de44cfc9c805565f6b125c11e8ba94001c725b [diff] |
[fuchsia] Implement SetContentAreaSettings in Frame FIDL API. Corresponding FIDL API change is in https://fxrev.dev/590185 The `SetContentAreaSettings` API merges existing APIs like `SetPreferredTheme` and `SetPageScale`. We will deprecate the `SetPreferredTheme` API in this CL. `autoplay_policy` was previously set on Frame initialization in `CreateFrameParams` is also moved to `SetContentAreaSettings`. - Changed `CreateFrameForWebContents` to return a pointer to the newly created Frame, and nullptr if a Frame could not be created. - Changed `SetWebPreferences` calls to be done through the Frame using `SetContentAreaSettings` API instead. - Improved consistency of `WebPreferences` when it is recomputed by Content layer. - Changed `FromWebContents` to return nullptr if web_contents is not yet owned by a Frame. Added `DCHECK` to callers to ensure previous invariant. - Added browser tests for `SetContentAreaSettings` API. - Improved error handling in `ThemeManager`. - Hide scrollbars in Cast Component. Bug: 1254073 Change-Id: I31c8e374b58cd3a4bb324ab3abb30bc3818e17da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3205636 Commit-Queue: David Song <wintermelons@google.com> Auto-Submit: David Song <wintermelons@google.com> Reviewed-by: Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/main@{#935191}
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.