Firefox main Tab not accessible after few pin tabs creation

RESOLVED WORKSFORME

Status

()

Firefox
Tabbed Browser
RESOLVED WORKSFORME
4 years ago
4 years ago

People

(Reporter: sridharanwins@gmail.com, Unassigned)

Tracking

23 Branch
x86_64
Windows 7
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

4 years ago
Created attachment 798739 [details]
bugzilla.PNG

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130814063812

Steps to reproduce:

Created a few tabs using pin tab option


Actual results:

Tabs pinned overlap the main Firefox menu, making it inaccessible


Expected results:

Pin tabs could have gone leaner or smaller or at least in the scroll mode

Updated

4 years ago
Group: core-security
Works fine for me on the latest Nightly:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
Build ID: 20130908030205

Reporter, could you please confirm whether the issue is still reproducible using Firefox in safe mode or with a new profile?
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Component: Untriaged → Tabbed Browser
Flags: needinfo?(sridharanwins)
(Reporter)

Comment 2

4 years ago
(In reply to Simona B [QA] from comment #1)
> Works fine for me on the latest Nightly:
> Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0
> Build ID: 20130908030205
> 
> Reporter, could you please confirm whether the issue is still reproducible
> using Firefox in safe mode or with a new profile?
> https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-
> mode
> https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-
> firefox-profiles


Resolved. Works fine. Thanks
Flags: needinfo?(sridharanwins)
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.