Tabs overlapping
Categories
(Firefox :: Tabbed Browser, defect, P3)
Tracking
()
People
(Reporter: sbelwal12, Unassigned)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression, steps-wanted)
Attachments
(4 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Open multiple tabs.
Actual results:
When opening multiple tabs, tabs overlap instead of being placed next to each other, leaving some blank space towards the left side (refer to attached file for more details).
Expected results:
The tabs should have been placed next to each other.
Comment 1•6 years ago
|
||
Does this happen after disabling all extensions and restarting Firefox? If you have a userChrome.css file, temporarily move it to a different folder before restarting.
I have not been able to reproduce the bug after disabling all extensions. But the issue occurs randomly, so, I'll keep trying to reproduce it.
Updated•6 years ago
|
The issue occured again, attached screenshot for the same.
Comment 6•6 years ago
|
||
(In reply to sbelwal12 from comment #3)
The issue occured again, attached screenshot for the same.
Was this with your add-ons disabled?
Yes. All the images of the overlapping issue are with all of my add-ons disabled.
Comment 8•6 years ago
|
||
Have you dragged any tabs before they started overlapping?
No, all I did was open multiple tabs.
Comment 10•6 years ago
|
||
Unfortunately without further information about when (with what Nightly build) the issues started, or how exactly it can be reproduced, this bug doesn't seem actionable.
Comment 11•6 years ago
|
||
When this happens, do you perhaps see any errors in the browser console?
Reporter | ||
Comment 12•6 years ago
|
||
I didn't notice that. I'll try to reproduce the issue and check for errors in the console.
Comment 14•5 years ago
|
||
Code sheriff Cristian had the issue again today with Firefox 69.0b13 on Windows 10. He dragged a tab from one window to a different one. The Browser Console didn't list errors when he checked (but Invalid chrome uri: /
- might be from an add-on). While be were setting up the browser toolbox and attaching it, the tab bar reset to its normal style.
Comment 15•5 years ago
|
||
(In reply to Sebastian Hengst [:aryx] (needinfo on intermittent or backout) from comment #14)
Code sheriff Cristian had the issue again today with Firefox 69.0b13 on Windows 10. He dragged a tab from one window to a different one.
This means this is likely a regression from bug 1355507, and bug 1396833 didn't fully fix this.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 16•5 years ago
|
||
I removed the regressionwindow-wanted tag because from comment 15 we know the regressor.
Comment 18•4 years ago
•
|
||
I can constantly reproduce this bug now with the use of the following flow.
The bug reproduced when I tried to move a few tabs into a new window of Firefox and a notification from irc/chat (element) was displayed in windows in the same time. Also, tabs cannot be closed, tapping on X does nothing. I use Firefox 85.0.2 (64-bit) on Windows 10 Enterprise.
Everything was fine after restarting the browser. Found these errors in Browser Console:
Security Error: Content at https://bugzilla.mozilla.org/show_bug.cgi?id=1536480 may not load or link to moz-extension://ae4ca2af-4bc7-4c17-aa2b-ff9caca357f9/template/panel-video-compact.html.
Security Error: Content at https://bugzilla.mozilla.org/show_bug.cgi?id=1536480 may not load or link to moz-extension://ae4ca2af-4bc7-4c17-aa2b-ff9caca357f9/template/panel-video-camera.html.
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 4
Security Error: Content at https://bugzilla.mozilla.org/show_bug.cgi?id=1628122 may not load or link to moz-extension://ae4ca2af-4bc7-4c17-aa2b-
Security Error: Content at https://www.google.ro/ may not load or link to moz-extension://ae4ca2af-4bc7-4c17-aa2b-ff9caca357f9/template/panel-video-compact.html.
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 312" data: no] FaviconLoader.jsm:312:24
[Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIContentSniffer.getMIMETypeFromContent]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: resource:///modules/FaviconLoader.jsm :: onStopRequest :: line 312" data: no] FaviconLoader.jsm:312:24
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xhtml
Error: Can't find profile directory. XULStore.jsm:66:15
Content Security Policy: Ignoring “'unsafe-inline'” within script-src or style-src: nonce-source or hash-source specified 4
Security Error: Content at https://bug1536480.bmoattachments.org/attachment.cgi?id=9053896 may not load or link to moz-extension://ae4ca2af-4bc7-4c17-aa2b-ff9caca357f9/template/panel-video-compact.html.
Security Error: Content at https://bug1536480.bmoattachments.org/attachment.cgi?id=9053896 may not load or link to moz-extension://ae4ca2af-4bc7-4c17-aa2b-ff9caca357f9/template/panel-video-camera.html.
this.window.gBrowserInit is undefined
Comment 19•4 years ago
|
||
Comment 21•4 years ago
|
||
(In reply to Cristian Brindusan [:cbrindusan] from comment #18)
I can constantly reproduce this bug now with the use of the following flow.
The bug reproduced when I tried to move a few tabs into a new window of Firefox and a notification from irc/chat (element) was displayed in windows in the same time.
That's bug 1593586.
Updated•3 years ago
|
Updated•2 years ago
|
Comment 22•2 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 7 See Also bugs.
:dao, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 23•2 years ago
|
||
I believe this has been addressed in bug 1593586 and bug 1753861. If there's work left to do, we'll need specific steps to reproduce and those are best off in a new bug - feel free to needinfo me if there are still situations where you see this with Firefox 110 or later (released next week).
Description
•