Roll PDFium from 85ec8cd41de4 to 17be9fefade8 (12 revisions)

https://pdfium.googlesource.com/pdfium.git/+log/85ec8cd41de4..17be9fefade8

2022-04-30 thestig@chromium.org Ignore attempts to set document properties via JS.
2022-04-29 thestig@chromium.org Remove useless V8 default GN args.
2022-04-29 thestig@chromium.org [Skia] Enable a FPDFProgressiveRenderEmbedderTest.
2022-04-29 thestig@chromium.org Roll build/ c7876b5a4..dd39b637a (140 commits)
2022-04-29 tsepez@chromium.org Explicitly call StringViewTemplate(char&) ctor in {Byte,Wide}String
2022-04-29 thestig@chromium.org Fix IWYU for std::back_inserter().
2022-04-29 thestig@chromium.org Roll tools/clang/ 548c2354f..c8e9f238a (11 commits)
2022-04-29 thestig@chromium.org Roll build/ b69813979..c7876b5a4 (123 commits)
2022-04-29 thestig@chromium.org Roll tools/clang/ 3a67a5003..548c2354f (2 commits)
2022-04-29 thestig@chromium.org Roll build/ ee10d9605..b69813979 (45 commits)
2022-04-29 thestig@chromium.org Roll third_party/abseil-cpp/ a13888fac..ef6cda346 (7 commits)
2022-04-29 thestig@chromium.org Roll v8/ 49d1fa9a2..c25a4438c (120 commits)

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 pdfium-deps-rolls@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://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug

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: I5cc25b9082058c84e97cfe520c91e299b7e353db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3617512
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@{#998040}
1 file changed
tree: dda50c02b91d098d813f2a749ae65b670c941437
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython
  61. .vpython3
  62. .yapfignore
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. ENG_REVIEW_OWNERS
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.