micro-editor / micro-editor/micro
Weird tab bar behavior
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 29.6k
- Forks
- 1.4k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 10
Description
The interaction between the tab bar and buffer window/pane seems to be seamless, which creates some cases where the user could be confused:
- mark a text section with the mouse while still pressing the left mouse button to move the selection up and reach a tab != the active one
- the inactive will become the active one
- my expectation is, that the tab bar should ignore these "triggers"
- "easy to fix" (ignore while the active tab still keeps the press), but could be just half of the truth since there are other strange cases
- the inactive will become the active one
- press the left mouse button over one tab and move the mouse while still pressing the button
- the next hovered tab becomes active
- intended?
- when the tab bar is left into the buffered text within the same action then the buffered text will be selected till the mouse button is released
- I don't expect that to happen, because the press was done within the tab bar
- the next hovered tab becomes active
Version: 2.0.14-dev.245
Commit hash: 2259fd10
OS: Debian testing (trixie)
Terminal: GNOME Console aka KGX 46.0
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the two mouse-drag scenarios on micro 2.0.14-dev.245 at commit 2259fd10: dragging a selection across tabs, and dragging from a tab into buffered text. Determine the intended tab-bar behavior for each path, then verify that tab activation and text selection match those expectations without affecting unrelated mouse interactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100