chore: Update Chrome (stable) to 138.0.7204.49 and Chrome (beta) to 139.0.7258.5

[github-actions]

This PR was auto-generated to update the version(s) of Chrome for driver tests

[cypress]

cypress    Run #63312

Run Properties:   Failed #63312  •  adc7dda28a: remove invalid attribute HTML test

Project	cypress
Branch Review	update-chrome-stable-from-137.0.7151.119-beta-from-138.0.7204.35
Run status	Failed #63312
Run duration	15m 14s
Commit	adc7dda28a: remove invalid attribute HTML test
Committer	Jennifer Shehane
View all properties for this run ↗︎

---

Test results
Failures	2
Flaky	2
Pending	10
Skipped	0
Passing	609
View all changes introduced in this branch ↗︎

UI Coverage  0%
Untested elements	4
Tested elements	0

Accessibility  97.09%
Failed rules	0 critical   1 serious   0 moderate   0 minor
Failed elements	4

---

Tests for review

  cypress/e2e/runner/ui-states.cy.ts • 2 failed tests • app-e2e

View Output

Test		Artifacts
src/cypress/runner ui states > status codes		Test Replay Screenshots
src/cypress/runner ui states > errors > long error		Test Replay Screenshots

  cypress/e2e/studio/studio.cy.ts • 2 flaky tests • app-e2e

View Output

Test		Artifacts
Cypress Studio > creates a new test for an existing spec with the url already defined		Test Replay Screenshots
Cypress Studio > does not remove the studio url parameters if saving fails		Test Replay Screenshots

[jennifer-shehane]

In Chrome 139: https://developer.chrome.com/blog/chrome-139-beta there is the following change:

• Allow more characters in JavaScript DOM APIs: The HTML parser has always (or for a long time) allowed elements and attributes to have a wide variety of valid characters and names, but the JavaScript DOM APIs that create the same elements and attributes are more strict and don't match the parser. This change relaxes the validation of the JavaScript DOM APIs to match the HTML parser.

This change causes this failure:

Where we are attempting to take a snapshot of this HTML and expecting the setAttributes to throw a failure.

From this area in the code: https://github.com/cypress-io/cypress/blob/develop/packages/driver/src/cy/snapshots.ts#L29

Chrome 138 behavior:

Chrome 139 behavior:

I could not actually find a way to set an invalid attribute in HTML anymore in Chrome 139. It's very forgiving! So I am removing this test. I suppose we could mock setAttribute throwing??

[cypress-bot]

Released in 14.5.1.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v14.5.1, please open a new issue.