Wrong hitbox (activation field) on the left tab arrow (button to scroll the tabs).
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr91 | --- | wontfix |
| firefox101 | --- | wontfix |
| firefox102 | --- | fix-optional |
| firefox103 | --- | ? |
People
(Reporter: smolny.2, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Top: Corner = no hitbox; Bottom: Mouse in the middle of the button = hitbox
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:100.0) Gecko/20100101 Firefox/100.0
Steps to reproduce:
Just open multiple tabs until arrows to scroll them shows up and then try hit left arrow just by moving your mouse to the very corner of the screen and then pressing LMB.
It dosen' matter which density i have (compact, normal, touch).
I'm using firefox on a windows 10 with 1920 × 1080 screen.
Actual results:
Activation field (hitbox) is to small and the mouse cannot hit this arrow while being in the corner.
Expected results:
I should have been able to hit this button just by doing this procedure mentioned above. I was able to do this before the proton version of the firefox.
|
||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox::Tabbed Browser' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•2 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=8aa1b80a8c6b66cccc2e37080fbf6197eee8d801&tochange=1716229005d8b97f305bd663b8bc8d3fec4a4f3a
|
|
||
Comment 3•2 years ago
|
||
:bigiri, since you are the author of the regressor, bug 1700109, could you take a look?
For more information, please visit auto_nag documentation.
|
||
Comment 4•2 years ago
|
||
I looked into this, I couldn't find the cause. The padding in the toolbar appears to be correct. While I did flip the preference for Proton, that preference enabled a lot of changes, Bug 1700109 is not the true regression for this. To find the true regression for this, I recommend testing older revisions with the browser.proton.enabled preference enabled.
Description
•