commit | 374888addcbefab05e8d3e9c4f806d18a135a9f5 | [log] [tgz] |
---|---|---|
author | chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> | Fri Feb 02 07:32:32 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Feb 02 07:32:32 2024 |
tree | 799fd0776163cb3813ab7426cab75b6c7a17b640 | |
parent | 283aaafd49baba51115413ce6523160ecf099037 [diff] |
Roll PDFium from 4d00d97379e8 to 7c7a6087e09e (2 revisions) https://pdfium.googlesource.com/pdfium.git/+log/4d00d97379e8..7c7a6087e09e 2024-02-01 thestig@chromium.org Add FPDFText_LoadCidType2Font() API 2024-02-01 thestig@chromium.org Encapsulate FT_Get_Glyph_Name() calls in CFX_Face If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/pdfium-autoroll Please CC dhoss@chromium.org,pdfium-deps-rolls@chromium.org,thestig@chromium.org on the revert to ensure that a human is aware of the problem. To file a bug in PDFium: https://bugs.chromium.org/p/pdfium/issues/entry To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Bug: None Tbr: pdfium-deps-rolls@chromium.org Change-Id: I6d7f5612d482109f0144e23dc6be3ffbc484333a Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5259048 Bot-Commit: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Commit-Queue: chromium-autoroll <chromium-autoroll@skia-public.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1255460}
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.