[UX] Close account console mobile nav after selecting a page - #51309
Merged
Conversation
edewit
approved these changes
Aug 4, 2026
edewit
enabled auto-merge (squash)
August 4, 2026 07:04
edewit
disabled auto-merge
August 4, 2026 07:05
Contributor
Author
|
Thanks for the review, @edewit. I've created and linked an issue and added Playwright tests which should cover both the desktop and mobile navigation. |
edewit
approved these changes
Aug 5, 2026
Contributor
|
super thank you |
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.broker.KcOidcBrokerTest#loginWithExistingUserWithBruteForceEnabledKeycloak CI - Java Distribution IT (windows-latest - temurin - 21) |
Contributor
Author
|
Looking at the test failure, this doesn't seem to have anything to do with this pull request:
This patch didn't modify any of the Java code. I don't think this patch broke that test. EDIT: Also rebased on top of the latest |
If you have ever used Keycloak's Account Console on mobile, you probably noticed some UI/UX annoyances. For example, if you open the main menu, click on another category (e.g. Signing-in), the new page will be loaded in the brackground, but you sont immediately notice since the page is still overlayed by the main menu and you have to realize that you have to close it manually to continue. This patch fixes that issue. It appeared onn narrow viewports (phones, or a desktop browser window resized below PatternFly's 1200px breakpoint). Signed-off-by: Lars Kiesow <lkiesow@uos.de>
This tests that on narrow viewports the sidebar nav is an overlay, and it must close after selecting a page instead of staying on top of the newly loaded content. A second test guards that desktop viewports keep the persistent sidebar open, so a future change can't silently drop the width check. Signed-off-by: Lars Kiesow <lkiesow@uos.de>
edewit
enabled auto-merge (squash)
August 5, 2026 13:53
eryx12o45
pushed a commit
to eryx12o45/keycloak
that referenced
this pull request
Aug 6, 2026
…k#51309) * Close account console mobile nav after selecting a page If you have ever used Keycloak's Account Console on mobile, you probably noticed some UI/UX annoyances. For example, if you open the main menu, click on another category (e.g. Signing-in), the new page will be loaded in the brackground, but you sont immediately notice since the page is still overlayed by the main menu and you have to realize that you have to close it manually to continue. This patch fixes that issue. It appeared onn narrow viewports (phones, or a desktop browser window resized below PatternFly's 1200px breakpoint). Signed-off-by: Lars Kiesow <lkiesow@uos.de> * Add Playwright test for mobile nav auto-close This tests that on narrow viewports the sidebar nav is an overlay, and it must close after selecting a page instead of staying on top of the newly loaded content. A second test guards that desktop viewports keep the persistent sidebar open, so a future change can't silently drop the width check. Signed-off-by: Lars Kiesow <lkiesow@uos.de> --------- Signed-off-by: Lars Kiesow <lkiesow@uos.de>
alehhu
pushed a commit
to alehhu/keycloak
that referenced
this pull request
Aug 8, 2026
…k#51309) * Close account console mobile nav after selecting a page If you have ever used Keycloak's Account Console on mobile, you probably noticed some UI/UX annoyances. For example, if you open the main menu, click on another category (e.g. Signing-in), the new page will be loaded in the brackground, but you sont immediately notice since the page is still overlayed by the main menu and you have to realize that you have to close it manually to continue. This patch fixes that issue. It appeared onn narrow viewports (phones, or a desktop browser window resized below PatternFly's 1200px breakpoint). Signed-off-by: Lars Kiesow <lkiesow@uos.de> * Add Playwright test for mobile nav auto-close This tests that on narrow viewports the sidebar nav is an overlay, and it must close after selecting a page instead of staying on top of the newly loaded content. A second test guards that desktop viewports keep the persistent sidebar open, so a future change can't silently drop the width check. Signed-off-by: Lars Kiesow <lkiesow@uos.de> --------- Signed-off-by: Lars Kiesow <lkiesow@uos.de> Signed-off-by: alehhu <159355663+alehhu@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you have ever used Keycloak's Account Console on mobile, you probably noticed some UI/UX annoyances. For example, if you open the main menu, click on another category (e.g. Signing-in), the new page will be loaded in the background, but you don't immediately notice since the page is still overlayed by the main menu and you have to realize that you have to close it manually to continue.
This patch fixes that issue. It appeared onn narrow viewports (phones, or a desktop browser window resized below PatternFly's 1200px breakpoint).
This closes #51423
EDIT: Rebased to current
main