4e9dea8d3d
Currently PDFium SDK determines whether to use Skia renderer in the renderer process, and it's determined by feature flag (it's a choice made by either the user or the finch experiment). An enterprise policy will be created to also control the decision on whether to use Skia renderer. Therefore the decision point needs to be moved into the browser process. This CL moves the feature flag check to the browser process before the PDF plugin is created, and sends a `use_skia` flag through the mime handler together with other PDF plugin attributes, so that the logic of checking enterprise policy can be added in the browser process in the future. Bug: 1440430 Change-Id: I8b74d493576f62be6231b872aec4018e7627a3b7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4481627 Reviewed-by: Sam McNally <sammc@chromium.org> Commit-Queue: Nigi <nigi@chromium.org> Reviewed-by: Matthew Denton <mpdenton@chromium.org> Reviewed-by: Lei Zhang <thestig@chromium.org> Cr-Commit-Position: refs/heads/main@{#1141525}
Chromium
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.