Closed
Bug 1483632
Opened 6 years ago
Closed 6 years ago
Pin tab shape is resizing if the page is loading in firefox 63 with browser.tabs.hideThrobber=true
Categories
(Firefox :: Theme, defect, P5)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: muzahewud, Unassigned)
References
Details
(Keywords: regression)
Attachments
(1 file)
|
86.17 KB,
image/jpeg
|
Details |
pinnedtab.jpg
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.12 Safari/537.36 OPR/56.0.3045.0 (Edition developer) Steps to reproduce: Load a site and click pin tab. The pinned tab is oddly shaped and then is resized properly. New profile with only browser.tabs.hideThrobber=true
Depends on: 1446101
Keywords: ux-error-prevention,
ux-interruption
OS: Unspecified → All
Hardware: Unspecified → All
Has Regression Range: --- → yes
Has STR: --- → yes
Component: Untriaged → Theme
|
||
Comment 2•6 years ago
|
||
Mark, can you please take a look if and how your patch caused this?
|
|
||
Updated•6 years ago
|
Priority: -- → P2
|
|
||
Comment 3•6 years ago
|
||
saproeno, why do you think this is related to bug 1446101?
Flags: needinfo?(muzahewud)
Keywords: ux-error-prevention,
ux-interruption
|
||
Comment 4•6 years ago
|
||
I just looked at the change I made in the follow up for that and it doesn't appear to make a difference.
Flags: needinfo?(mstriemer)
(In reply to Dão Gottwald [::dao] from comment #3) > saproeno, why do you think this is related to bug 1446101? mozregression
Flags: needinfo?(muzahewud) → needinfo?(dao+bmo)
|
|
||
Comment 6•6 years ago
|
||
browser.tabs.hideThrobber is a Nightly-only pref for performance analysis, end users aren't supposed to touch this.
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(dao+bmo)
Priority: P2 → P5
Resolution: --- → WONTFIX
Summary: Pin tab shape is resizing if the page is loading in firefox 63 → Pin tab shape is resizing if the page is loading in firefox 63 with browser.tabs.hideThrobber=true
|
||
Updated•6 years ago
|
Keywords: regression
You need to log in
before you can comment on or make changes to this bug.
Description
•