microsoft / playwright · Issue No. 42795

[Bug]: WebKit projects fail to store input files in IndexedDB

Openby BeeDiceopened Sep 19, 2026updated Sep 19, 20261 comments

Description

Version

1.63.0

Steps to reproduce

Clone https://github.com/BeeDice/playwright-webkit-file-idb-bug
npm install
npm run test

The repo has an HTML file with a file input element. On file select, it stores the File object in IndexedDB and notifies the user of success via a span element. The Playwright test uses setInputFiles to set a dummy text file on the file input.

Expected behavior

The span element should indicate that the selected File object has been stored in IndexedDB. You can see that happen in the Chromium test, or, by manually reproducing the test in Safari (open the HTML file, select the fixture text file, and notice the span updates).

Actual behavior

On Webkit, via Playwright, the span does NOT update, and the test times out.

Additional context

There is no console output in Playwright. Presumably, this means that the IndexedDB transaction is stalling indefinitely. I have tried upping the timeout to 10 seconds but it does not help. When reproducing the test manually (as described above), the transaction completes successfully on the order of miliseconds.

Environment

System:
    OS: macOS 26.6.2
    CPU: (10) arm64 Apple M4
    Memory: 2.75 GB / 16.00 GB
  Binaries:
    Node: 24.7.0 - /Users/danmaftei/.nvm/versions/node/v24.7.0/bin/node
    npm: 11.5.1 - /Users/danmaftei/.nvm/versions/node/v24.7.0/bin/npm
  IDEs:
    Codex: 0.155.1 - /opt/homebrew/bin/codex
  Languages:
    Bash: 3.2.57 - /bin/bash

Relay Analysis

View on GitHub

Relay reads this issue against the repository's contribution signals: the files it is likely to touch, how the maintainers triage work this size, and what the first contribution would exercise.

The full analysis for this issue is still being assembled. Until then, the description above and the thread on GitHub are the most reliable context.