Roll PDFium from b019686a0e95 to 51cfc0f629ad (10 revisions)

https://pdfium.googlesource.com/pdfium.git/+log/b019686a0e95..51cfc0f629ad

2024-11-22 tsepez@chromium.org Move all the C code for jpeg to the C file.
2024-11-22 tsepez@chromium.org Consolidate error_fatal() into jpeg_common.h
2024-11-22 tsepez@chromium.org Consistently store JpegCommon into cinfo.client_data.
2024-11-22 tsepez@chromium.org Rename jpegmodule member and set consistently.
2024-11-22 tsepez@chromium.org Move setjmp() calls from .cpp to .c files.
2024-11-21 thestig@chromium.org Test FPDFPageObj_SetIsActive() with nullptr input
2024-11-21 thestig@chromium.org Mark function scope constexpr constants as static in tests
2024-11-21 thestig@chromium.org Fix potential compiler error in CPDF_ToUnicodeMap::HandleBeginBFChar()
2024-11-21 thestig@chromium.org Add test for FPDFPageObj_SetIsActive() interaction with text objects
2024-11-21 awscreen@chromium.org Add FPDFPageObj_GetIsActive() experimental API

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 awscreen@google.com,dhoss@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: chromium:377660088,chromium:379259821
Tbr: awscreen@google.com
Change-Id: Ie176c6da77eb8e2ad847454b89757c29f1503b03
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6044180
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@{#1387005}
2 files changed
tree: 5a32368eda0ed0997a758c547dbc49d27b2cabc7
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. WATCHLISTS
README.md

Logo 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.