Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reset current branch - tab order #7481

Closed
mstv opened this issue Dec 3, 2019 · 0 comments · Fixed by #7482
Closed

Reset current branch - tab order #7481

mstv opened this issue Dec 3, 2019 · 0 comments · Fixed by #7482

Comments

@mstv
Copy link
Member

mstv commented Dec 3, 2019

Current behaviour

On open, no focus is visible. The tab order is almost random or opposite.

Expected behaviour

The pre-selected radion button is focused on open.
Logical tab order.

Steps to reproduce

  • Reset current branch to here...
  • hit Tab 4x
  • hit Down (sic!) several times

Screenshots

ResetCurrentBranch

Did this work in previous version of GitExtensions

at least not since the recent extension

Environment

  • Git Extensions 3.3.0
  • Build 69763de058580d0dbf84be9a2d725b1719f607c6
  • Git 2.23.0.windows.1
  • Microsoft Windows NT 10.0.18362.0
  • .NET Framework 4.8.4018.0
  • DPI 96dpi (no scaling)
@gerhardol gerhardol added type: bug 🐛 up-for-grabs Easy tasks for those looking to get involved. Refer to https://up-for-grabs.net/ area: user experience type: regression regression, normally to latest official release labels Dec 3, 2019
@ghost ghost added the 🚧 status: in progress Issues which have associated PRs label Dec 3, 2019
@ghost ghost removed the 🚧 status: in progress Issues which have associated PRs label Dec 3, 2019
@RussKie RussKie removed up-for-grabs Easy tasks for those looking to get involved. Refer to https://up-for-grabs.net/ type: regression regression, normally to latest official release labels Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants