-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Fitts' Law to the tab bar #3510
Comments
Yes please! 👍 |
I actually like the idea. Maybe Windows Terminal should just behave more like Chrome and Firefox. |
Yea this makes sense to me. I could have sworn there was a dupe for this but I'm not finding it. Thanks for the write-up! |
@cinnamon-msft is going to find where this goes. She's working on tab pixel-y things right now. |
Kayla says (now verbally in triage) that this is a /dup of #2541. |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
Description of the new feature/enhancement
Currently, there are 4 pixels of distance between each of the top of the tabs and the top of the maximized window:
According to the Fitts' Law, the time to interact with a component is a function of the distance from the mouse pointer to the component, and the area of the component. As a special case, because the computer screen is bounded, the four screen borders (and the four corners) have infinite area, making them extremely easy and fast to use.
However, the Windows Terminal (version 0.6.2951.0) places the tabs just 4 pixels away from the screen border, making it very frustrating to click (even more so because users are already used to tabs in Chrome and Firefox).
Further reading:
Proposed technical implementation details (optional)
The tabs should touch the screen border when the terminal is maximized. Just like how Chrome and Firefox also behave.
Footnote: I tried searching if this issue had been reported before, but I found nothing. This issue here should be included into #1625.
The text was updated successfully, but these errors were encountered: