You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Keyboard focus is getting lost after activating home control in left navigation pane in windows. #2600
User Impact:
Keyboard dependent users will find it difficult to identify the currently focused element if keyboard focus is getting lost after activating home control in left navigation pane in windows.
Refer Attachment:
Keyboard focus get lost after activating Home tab item present in left navigation pane.mp4
Keyboard focus shouldn't be lost home tab item after activating it, it should remain on the home control.
Actual behavior
Keyboard focus is getting lost after activating home control in left navigation pane in windows.
On press tab key, focus is moving to 'Github' control.
Thanks very much for reporting this issue @msftedad . Docsify v5 is in release candidate status, and various accessibility issues have been addressed in the release.
I tried to step through your helpful video and I think that focus is no longer lost in the navigation panel, could you please confirm? You can access the latest Docsify v5 release candidate at https://preview.docsifyjs.org
Hi @paulhibbitts, Thanks for the update. As verified this issue on the given Docsify v5 release https://preview.docsifyjs.org/ The issue has been partially resolved. Currently, after selecting any control from the left pane, the keyboard focus is lost and not visible. Pressing the Tab key once makes the focus appear on the main page.
Expected behavior: After expanding any expandable button in the left pane, the focus should remain on the same control in the left pane. And when a user selects any control from the expanded list in the left pane, the focus should either move to the corresponding control on the main page or remain on the selected control.
Hello @msftedad , thank you for your patience. Could you please try the Preview Build at #2740 and confirm that it addresses this issue? Thank you very much.
Hi @paulhibbitts, Thank you for the update. It appears that we do not currently have access to the Preview Build (#2740) required to verify this fix. Could you please advise on how we can access the preview build or suggest an alternative way to validate the fix?
Thanks for looking into this. We will share these findings with our development team for further review. If we have any additional questions or require further clarification, we will reach out.
This is a good candidate for a keyboard regression test. After activating the home control, focus should land on a predictable element, such as the new page heading or the active navigation link, rather than being dropped to the document. A Playwright test that tabs to the control, presses Enter, and checks document.activeElement would make the accessibility fix concrete.
Activity
paulhibbitts commentedon Sep 5, 2025
Thanks very much for reporting this issue @msftedad . Docsify v5 is in release candidate status, and various accessibility issues have been addressed in the release.
I tried to step through your helpful video and I think that focus is no longer lost in the navigation panel, could you please confirm? You can access the latest Docsify v5 release candidate at https://preview.docsifyjs.org
msftedad commentedon Sep 10, 2025
Hi @paulhibbitts, Thanks for the update. As verified this issue on the given Docsify v5 release https://preview.docsifyjs.org/ The issue has been partially resolved. Currently, after selecting any control from the left pane, the keyboard focus is lost and not visible. Pressing the Tab key once makes the focus appear on the main page.
Expected behavior: After expanding any expandable button in the left pane, the focus should remain on the same control in the left pane. And when a user selects any control from the expanded list in the left pane, the focus should either move to the corresponding control on the main page or remain on the selected control.
msftedad commentedon Oct 29, 2025
Hi Team,
Any update on this issue?
paulhibbitts commentedon Nov 7, 2025
Any follow-up thoughts @sy-records ?
sy-records commentedon Nov 7, 2025
I'm not sure how to fix it at the moment.
3 remaining items
fix: preserve sidebar focus on desktop after navigation (docsifyjs#2600)
paulhibbitts commentedon Jun 6, 2026
Hello @msftedad , thank you for your patience. Could you please try the Preview Build at #2740 and confirm that it addresses this issue? Thank you very much.
msftedad commentedon Jun 8, 2026
Hi @paulhibbitts, Thank you for the update. It appears that we do not currently have access to the Preview Build (#2740) required to verify this fix. Could you please advise on how we can access the preview build or suggest an alternative way to validate the fix?
paulhibbitts commentedon Jun 8, 2026
Sorry about that @msftedad , please try this link: https://docsify-preview-git-fork-puneetdixit200-fix-si-be1d9f-docsifyjs.vercel.app/
msftedad commentedon Jun 10, 2026
@paulhibbitts, Thank you for the update.
We verified the issue using Preview Build https://docsify-preview-git-fork-puneetdixit200-fix-si-be1d9f-docsifyjs.vercel.app/. Although the controls appear to be different in this build, we were unable to reproduce the reported issue.
Thanks for looking into this. We will share these findings with our development team for further review. If we have any additional questions or require further clarification, we will reach out.
Thank you.
paulhibbitts commentedon Jun 10, 2026
Thanks for confirming this fix in #2740 addresses this issue @msftedad !
hiSandog commentedon Jul 1, 2026
This is a good candidate for a keyboard regression test. After activating the home control, focus should land on a predictable element, such as the new page heading or the active navigation link, rather than being dropped to the document. A Playwright test that tabs to the control, presses Enter, and checks
document.activeElementwould make the accessibility fix concrete.paulhibbitts commentedon Jul 1, 2026
Thanks for the suggestion @hiSandog , perhaps after the release of Docsify v5 we could loop back to this. Also, a PR would always be welcome as well.
sy-records commentedon Sep 2, 2026
It looks like this has been fixed, so I'll close it for now.
If there are still issues, please reopen it.
trusktr commentedon Sep 9, 2026
Reopening because the fix isn't merged yet.