Skip to content

Fix: Turn on PdfOopif for PDF viewer (#2629)#3273

Merged
kblok merged 1 commit intomasterfrom
implement-upstream-change-2629
Mar 2, 2026
Merged

Fix: Turn on PdfOopif for PDF viewer (#2629)#3273
kblok merged 1 commit intomasterfrom
implement-upstream-change-2629

Conversation

@kblok
Copy link
Copy Markdown
Member

@kblok kblok commented Mar 2, 2026

Summary

  • Enable PdfOopif Chrome feature flag in the launcher to support PDF viewer in out-of-process iframes
  • Add pdf-viewer.html and sample.pdf test assets
  • Add two new OOPIF tests: ShouldExposeFunctionOnAPageWithAPdfViewer and ShouldEvaluateOnAPageWithAPdfViewer

Upstream Reference

Port of puppeteer/puppeteer#12370.

Chrome's PDF viewer replaces inner iframes with extension web views, which are not supported by Puppeteer. Enabling PdfOopif makes Chrome use out-of-process iframes for PDF viewing instead, which Puppeteer already supports.

Changes

File Change
ChromeLauncher.cs Added PdfOopif to default enabled Chrome features
OOPIFTests.cs Added two new PDF viewer tests
wwwroot/pdf-viewer.html New test asset - HTML page embedding a PDF iframe
wwwroot/sample.pdf New test asset - minimal PDF file

Test plan

  • Both new tests pass with Chrome/CDP
  • All 27 OOPIF tests pass (no regressions)

🤖 Generated with Claude Code

Enable PdfOopif feature flag in Chrome launcher to support PDF viewer
in out-of-process iframes. Add tests for exposeFunction and evaluate
on pages with embedded PDF viewers.

Port of upstream puppeteer/puppeteer#12370.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@kblok kblok merged commit b9041a9 into master Mar 2, 2026
14 checks passed
@kblok kblok deleted the implement-upstream-change-2629 branch March 2, 2026 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant