New Tab Button: Fitts' Law |
||||||||
Issue descriptionThe New Tab button should take advantage of Fitts' Law appropriately in refresh. We certainly don't extend to the window side edge, we may not be correct in how we extend to top. 2 days, mostly because I need to worry about things like "is TRAILING actually at the window edge". P2; we shouldn't ship without this (and we probably don't want to wait too long on it because it makes the LEADING position more sensical).
,
Jun 1 2018
Note to self: if the NTB is after the tabs, make sure the first tab gets Fitts' Lawed.
,
Jun 18 2018
Note to self: Be careful about assuming that LEADING means "at window left edge" -- it may not for CrOS teleported windows (see bug 834524 ).
,
Jun 28 2018
The NTB is now in the trailing position. It's not clear that we need this for the first tab for M69. If the first tab absolutely needs special treatment, let's open a new bug.
,
Jun 28 2018
Let's leave this open for ensuring the vertical extension is correct and for handling horizontal extension for LEADING/TRAILING (since we're not closing the door on future use of those yet) but P3 it as not-blocking-ship-anymore.
,
Jun 30 2018
the new tab button position is a terrible mistake. yet another reason to dump chromium, along with it's retarded 3-month hardcoded browsing history limit. thank god firefox is usable nowadays... goodbye chrome.
,
Jun 30 2018
Using the same position we've always used is a terrible mistake?
,
Jul 1
" @17: This is working as designed. Pinning the new tab button to a fixed position allows it to be more easily targeted as the number of tabs changes, but it's not going to change where new tabs open, since disturbing the order of the initial tabs in the strip breaks a lot of workflows. "
- pkasting@chromium.org (On issue 822063 )
The new position of the NTB (Fixed at the left before the tabs <Windows>), was
perfect, after getting used to it(It DEFINITELY needed some getting used to).
In Chrome canary 69.0.3478.0, NTB is switched back to the old pre-material refresh style. Please tell me this is a bug and not intended behaviour.
,
Jul 1
While there are reasons why a fixed NTB position has advantages (as you quote above), after testing, feedback, and reflection, the decision is to leave the NTB after the tabs as it was in previous versions of Chrome. So it is intended behavior, not a bug.
,
Jul 1
Bummer, I liked the fixed position. I think it would have been problematic in Chrome OS when using multi-profile mode though.
,
Jul 2
The fixed New Tab button is so much better that there should be an option in the settings, it's definitely worth the added complexity. You're right to not switch it on people though, there would be backlash. Also, maybe have the new tab button fixed on new installs?
,
Jul 12
,
Jul 16
Issue 857078 has been merged into this issue.
,
Jul 26
,
Aug 27
,
Sep 13
,
Sep 14
Failure to conform to Fitts Law only happened in the case described by issue 863228 (mixed-monitor DPI mode on Windows). This bug was fixed as a side effect of https://chromium-review.googlesource.com/c/chromium/src/+/1214747 Now the New Tab button should have a hit-test area that touches the top of the window whenever Chrome is maximized. I'm marking this fixed but we should verify on all affected platforms.
,
Sep 14
I suspect this isn't actually fixed for LEADING/TRAILING NTB positions but I also suspect that the likelihood of those ever shipping is dropping, so maybe it doesn't matter. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by pkasting@chromium.org
, Jun 1 2018