-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Add repo file tree middle click open #34730
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
Open
bytedream
wants to merge
10
commits into
go-gitea:main
Choose a base branch
from
bytedream:mouse-wheel-click-file-tree
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
50bf708
Open new tab when clicking file tree with mouse wheel
bytedream 83e925a
Use own function instead
bytedream 0941d5f
Merge branch 'main' into mouse-wheel-click-file-tree
bytedream 91069cf
use click.middle instead of auxclick
bytedream 2b5e119
also check if ctrl key was pressed
bytedream 7fef0bb
Merge branch 'main' into mouse-wheel-click-file-tree
bytedream 06ac1c9
update comment
bytedream 10d9471
check meta key in addition to ctrl
bytedream 9c4a8e2
add aux click check to doLoadDirContent
bytedream 9915581
add sub module aux click support
bytedream File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything is handled in
@click.stop
, so the@click.middle.stop
should be removed?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@click.stop
does not fire for aux clicks.@click.middle.stop
is transformed into amousup
event by vue internally, which is able to recognize aux clicks.@auxclick.stop
also exists, but Safari only added support for it lately, so it may not work for some users with older browsers.@click.stop
only fires if the click is released on the same button where it was pressed. The mouseup event always fires when the click is released, regardless of the starting point. This difference in behavior is why I didn't unify both handlers into a single@mouseup.stop
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But that's the expected behavior.
For example, if you "mousedown" in a normal
<a>
, then move mouse out, the link won't open.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What I just wanted to say is that I didn't unify both calls into a mouseup because that would mess with the current behavior
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would happen if "Ctrl+LeftClick"? I guess it won't trigger
click.middle
?