Repository navigation
Forms IT tests breaks with Chrome 136.0.7103.59 #39540
Description
Before reporting an issue
- I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.
Area
No response
Describe the bug
When running with the latest version of chrome 136.0.7103.59, tests like BrowserButtonsTest.appInitiatedRegistrationWithBackButton fail on chrome
Version
main
Regression
- The issue is a regression
Expected behavior
Tests should pass
Actual behavior
Tests fail, see https://github.com/keycloak/keycloak/actions/runs/14880473986/job/41808705885?pr=39522 and https://github.com/keycloak/keycloak/actions/runs/14885132071/job/41803271126
How to Reproduce?
See CI. Also tested locally.
Anything else?
No response
Metadata
Metadata
Assignees
Labels
Type
Fields
No fields configured for issues without a type.
Activity
[-]Forms IT tests break with Chrome 136.0.7103.59[/-][+]Forms IT tests breaks with Chrome 136.0.7103.59[/+]Downgrade Chrome to unblock CI
Downgrade Chrome to unblock CI
Downgrade Chrome to unblock CI
ahus1 commentedon May 7, 2025
@mposolda / @rmartinc - when testing this locally it was consistently failing for Chrome 136.0.7103.59 locally, so I downgraded to 135.0.7049.114 and then the test started to work again.
The workaround is now part of a097c5a which should now log the version used in the tests which was a bit hard to find out from the previously known good test.
I would appreciate if the core-clients team would have a look. With the workaround, the release branches are unblocked (first main, and as soon as we backport #39537 also 26.2
Thanks!
Downgrade Chrome to unblock CI
ahus1 commentedon May 8, 2025
See comment: a403ff0#r156592758
4 remaining items
Refresh back button for chrome 136
Refresh back button for chrome 136
Refresh back button for chrome 136
ahus1 commentedon May 9, 2025
@rmartinc - what are your plans for 26.0? Do you plan to backport it to that release branch as well? If yes, please also cherry-pick my workaround first to avoid conflicts.
rmartinc commentedon May 9, 2025
@ahus1 In 26.0 we are using chrome 134 fixed. IIRC there are two issues we should backport to moveto curent chrome in 26.0 (this one and the one about the
passworddetected at leaked by the browser).ahus1 commentedon May 9, 2025
Thank you for pointing me to how it works in 26.0. IMHO staying with a fixed version of Chrome in 26.0 might be sufficient. If anything breaks with a newer browser, we'll see it in 26.2 first and then hopefully consciously decide if we want to backport it to 26.0 or not.
Refresh back button for chrome 136