Coloured strip on Top of Tab is not clickable
Categories
(Firefox :: Tabbed Browser, defect)
Tracking
()
People
(Reporter: eros_uk, Unassigned)
Details
(Keywords: regression, regressionwindow-wanted, Whiteboard: [qa-regression-triage])
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Within that last few updates, the coloured strip on top of the tab no longer has a click event listener in order to make the tab active.
While it seem like a tiny section, many users (myself included) who maximise browser to the display, move the mouse to the top of the tab (top edge of the display i.e. as far a the mouse goes) (it is faster that way) to select a tab. Recently, it fails to activate the tab until the rest of the tab strip is clicked.
Updated•6 years ago
|
Comment 1•6 years ago
|
||
(In reply to erosman from comment #0)
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Steps to reproduce:
Within that last few updates, [...]
Could you help find out when exactly this broke using mozregression?
I use Firefox Nightly for extension development and with a few updates per day to nightly, it will takes many installations/regressions. IS not possible to check the HTML/XUl?
Comment 3•6 years ago
|
||
(In reply to erosman from comment #2)
I use Firefox Nightly for extension development and with a few updates per day to nightly, it will takes many installations/regressions.
mozregression does that for you, so you won't have to download and install many versions yourself, and it won't affect your standard Nightly profile either.
Does it have a portable instal?
Can it be done without installing new software on my development computer (with very strict settings)?
Comment 5•6 years ago
|
||
Yeah, it's just an executable that you should be able to run without administrator rights.
No, it actually installed it in my system folder. It is NOT portable.
Is it going to alter the current Firefox that I am running OR create a new Firefox application?
I do not wish to alter my current development Firefox applications since some of changes are NOT regress-able or revertible. A good example is the storage conversion to IndexedDB which is not revertible.
Comment 8•6 years ago
|
||
It's completely independent from whatever version of Firefox you're using.
It would be better for someone who is familiar with the regression process to find it out.
Updated•5 years ago
|
Reporter | ||
Comment 10•5 years ago
|
||
Note: It is possible that the problem might !! be that there is extra space (padding etc) between to top edge of the tab and the background browser container and moving the mouse to the top most edge causes the click to hit there !! (just a thought)
If browser is not active (top most application), clicking the above mentioned space causes the browser to become active but doesn't make the tab active.
Comment 11•5 years ago
|
||
I have attempted to reproduce this issue in order to try and find its regressor. I cannot reproduce it or I am missing some bits of information.
The steps I took are the following:
- Open browser (with a newly created profile).
- Maximize it.
- Open a few tabs.
- Navigate between tabs by left-clicking on the "upmost" position possible of the tab (edge of the screen).
Issue: Tabs would not be selected.
Actual: The tabs got selected.
I have tested in both Windows7 and Windows10, on Nightly v69.0a1 and Beta v68.0b7.
Considering all the above, I will ask the reporter to try again.
erosman, can you retry to reproduce this issue in a newly created profile?
You have the steps here: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager
Thank you for your contribution.
Updated•5 years ago
|
Reporter | ||
Comment 12•5 years ago
|
||
(In reply to Bodea Daniel [:danibodea] from comment #11)
Thank you for testing it.
The strangest thing has happened......
- I was on normal profile and the issue was present when I was reading your post
- I restarted Firefox with a clean profile, as you have mentioned, the issue was NOT present
- I restarted Firefox with normal profile ... and .. the issue disappeared !!??
It is fine now. I have no idea what has happened (something must have caused Firefox to reread/refresh something due to profile change).
This bug can be closed now. Sorry for the inconvenience.
Updated•5 years ago
|
Description
•