Closed
Bug 1366473
Opened 7 years ago
Closed 7 years ago
Sometimes all tabs have close buttons when overflowing
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
VERIFIED
FIXED
Firefox 55
People
(Reporter: dao, Assigned: dao)
References
Details
Attachments
(1 file)
I sometimes see this after restoring my session. This is likely a regression from bug 1356655. I think there's a race condition due to adjustTabstrip being called from a timeout via _handleNewTab: http://searchfox.org/mozilla-central/rev/24c443a440104dabd9447608bd41b8766e8fc2f5/browser/base/content/tabbrowser.xml#2358-2360
Comment hidden (mozreview-request) |
Comment hidden (mozreview-request) |
Comment 3•7 years ago
|
||
mozreview-review |
Comment on attachment 8869695 [details] Bug 1366473 - Explicitly hide close buttons in background tabs when overflowing. https://reviewboard.mozilla.org/r/141272/#review145098 The patch looks good (so r=me), but that setTimeout seems nasty; do we still need it? (sorry for the delay, I thought I had hit 'publish' on this review yesterday :-/)
Attachment #8869695 -
Flags: review?(florian) → review+
Assignee | ||
Comment 4•7 years ago
|
||
(In reply to Florian Quèze [:florian] [:flo] from comment #3) > Comment on attachment 8869695 [details] > Bug 1366473 - Explicitly hide close buttons in background tabs when > overflowing. > > https://reviewboard.mozilla.org/r/141272/#review145098 > > The patch looks good (so r=me), but that setTimeout seems nasty; do we still > need it? Yes, because _handleNewTab needs to know whether the tab got selected after the addTab call.
Comment hidden (mozreview-request) |
Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/a8d70b131270 Explicitly hide close buttons in background tabs when overflowing. r=florian
Comment 7•7 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a8d70b131270
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 55
Comment 8•7 years ago
|
||
I managed to reproduce this bug using the Nightly from 2017-05-20 both on Windows 10 x64 and Ubuntu 16.04 x64. Then I retested using the latest Nightly and Firefox 55.0b13 by opening a lot of new tabs and restarting the browser a few times on Mac Os 10.12, Windows 10 x64 and Ubuntu 16.04 x64 and the bug is not reproducing anymore. I think it's fixed.
Comment 9•7 years ago
|
||
(In reply to Oana Botisan from comment #8) > I managed to reproduce this bug using the Nightly from 2017-05-20 both on > Windows 10 x64 and Ubuntu 16.04 x64. Then I retested using the latest > Nightly and Firefox 55.0b13 by opening a lot of new tabs and restarting the > browser a few times on Mac Os 10.12, Windows 10 x64 and Ubuntu 16.04 x64 and > the bug is not reproducing anymore. > I think it's fixed. I can confirm Oana's findings on both 55.0b13 and 56.0a1. I believe it's safe to mark this verified, thank you Oana!
You need to log in
before you can comment on or make changes to this bug.
Description
•