[Regression]: enabling then filling a textarea doesn't fill it on chromium

[jnizet]

Last Good Version

1.52.0

First Bad Version

1.53.0

Steps to reproduce

1. Clone the repo git@github.com:jnizet/playwright-repro.git
2. pnpm install
3. pnpm start
4. open http://localhost:4200, click on the button, enter text in the textarea, see that everything works fine
5. kill the pnpm start process (Ctrl-C)
6. pnpm e2e --ui
7. run the test with the three configured browsers

Expected behavior

I expect the test to pass in the 3 browsers.

Actual behavior

The test fails on chromium. Filling the textarea after enabling it by clicking the button doesn't actually fill it.

Additional context

The test fails on my machine, but the repro was made after a similar scenario failed in a real app, in a github action, using Ubuntu.

Environment

System:
    OS: macOS 15.4.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 4.05 GB / 64.00 GB
  Binaries:
    Node: 20.19.2 - ~/.nvm/versions/node/v20.19.2/bin/node
    npm: 10.8.2 - ~/.nvm/versions/node/v20.19.2/bin/npm
    pnpm: 8.15.5 - ~/.nvm/versions/node/v20.19.2/bin/pnpm
  IDEs:
    VSCode: 1.100.0 - /usr/local/bin/code
  Languages:
    Bash: 3.2.57 - /bin/bash
  npmPackages:
    @playwright/test: 1.53.0 => 1.53.0 
    playwright-ng-schematics: 2.1.0 => 2.1.0

[yusufozturk-via]

it is same for me .It works for version 1.52.0.But for version 1.53.0 it fails on chromium

[Skn0tt]

Thanks for the report. Bisecting shows that b820ebd regressed this. Let me check what changed in that browser build.

[Skn0tt]

This is the chromium commit range that caused it: https://chromium.googlesource.com/chromium/src/+log/ffcf1767a10645545dbc83f1778e811c063f73ed..81e05bcca809d756c3a993618d7c8fbeedc38e41
Out of those, I'd guess it was https://chromium.googlesource.com/chromium/src/+/bc1d9a3ea94b44a7016140f2bbee649cdd1e30f5.

The bug is fixed on latest chromium, so we can release a fix with that version.

[yusufozturk-via]

Thanks for info. How do we update the chromium version, or when will you release a fix? @Skn0tt

[Skn0tt]

I'm expecting us to release a fix in the coming days. If need to unblocked yourselves now, you can either revert to v1.52, or use playwright@next: https://playwright.dev/docs/canary-releases

[jnizet]

Thanks @Skn0tt

[okobets]

I can repro this. Following

[dgozman]

This should be fixed by #36301.