In-app browser silently ignores window.print() and print-preview requests

Summary

Web applications that invoke the browser print preview do not open a print dialog in the Codex desktop app in-app browser. The triggering application behaves as if printing started, but nothing visible happens and no error is shown.

Environment

• Product: Codex desktop app, in-app browser
• Platform: macOS
• Site used to reproduce: Canvas LMS New Quizzes
• Observed: August 7, 2026

Steps to reproduce

1. Open Canvas LMS in the Codex in-app browser.
2. Open a Canvas New Quiz.
3. Select More Quiz Actions.
4. Select Print Key (With Answers) or Print Blank Quiz.
5. Canvas displays its Print Quiz dialog.
6. Click Print Preview.

Actual result

• The Canvas Print Quiz dialog closes.
• No macOS print dialog or print-preview window appears.
• No new browser tab is created.
• No error or unsupported-feature message is displayed.
• From the user perspective, the button does nothing.

I reproduced this while inspecting the page: the web dialog closed, the page URL remained unchanged, no JavaScript dialog appeared, and no additional browser tab was created.

Expected result

The in-app browser should open the native print dialog or provide an equivalent print-to-PDF workflow.

If native printing cannot be supported, it should detect the print request and explain that printing is unavailable, ideally offering one of these alternatives:

• Open the page in the system browser.
• Download the rendered page as a PDF.
• Generate a printable PDF directly.
• Copy the current URL for opening externally.

Impact

This prevents users from printing or saving PDFs from sites that rely on window.print(). It is especially confusing because the website dialog closes successfully, making the action appear broken rather than unsupported.