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
Unable to left-click on a file that overflow horizontally in the Commit Details View Files View #420
Comments
Hi @Wosi, Thanks for making me aware of this, upon initial inspection this seem to be more of a Chromium rendering quirk, as the DOM elements and JS doesn't change as a result of a record in the File View being abbreviated (i.e. the event handler is still on the element to capture mouse clicks). I'll look into what's causing this, and work out an alternative method to avoid this issue. In the meantime, you should still be able to right click on the files in the File Tree to access all of the available actions. |
Thanks, @mhutchie! |
Hi @Wosi, I just did some regression testing on this, and I found that this rendering quirk began occurring in Git Graph 1.27.0, after an additional This also means that in the meantime you also have the option to "Install another Version..." of the extension (Git Graph 1.26.0 will work fine), however you'll lose the new feature of the right-click context menu to run any of the available actions on each file. |
…n the Commit Details View Files View from being left-clicked. This issue was introduced with #381.
Thanks again for raising this bug so I could get it fixed! I'm currently looking to bring the release of Git Graph 1.28.0 sooner if possible (from 29/11/2020 to early next week). This will be available in v1.28.0. If you'd like to use it before the next release, you can download v1.28.0-beta.2, and install it following the instructions provided here. |
Wow, that was quick, thank you! |
The GIF shows the problem:
Environment
⚠ Please make sure you complete all of the required sections of this template. Without this required information, it will be harder to replicate this bug, and cause additional delays in resolving it.
The text was updated successfully, but these errors were encountered: