Session Restore button in tabstrip has janky animation

RESOLVED FIXED in Firefox 56

Status

()

RESOLVED FIXED
2 years ago
a year ago

People

(Reporter: ewright, Assigned: ewright)

Tracking

unspecified
Firefox 56
Points:
---

Firefox Tracking Flags

(firefox56 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

2 years ago
After turning on the pref in my own Nightly, I noticed that the animation is very jittery. As well, many times when clicked, the button animates small but does not fully disappear.
Comment hidden (mozreview-request)
(Assignee)

Comment 3

2 years ago
current patch changes: 
Button animates at same speed as new tabs open to appear smoother (100ms).
Padding removed from inner label so it smoothly goes to width of 0.
Setting the max-width of the sessionRestoreButton when it is first created, and removing the 'requestAnimationFrame', otherwise sometimes the listener will not catch the animation in time, resulting in not fully removing the button.

Comment 4

2 years ago
mozreview-review
Comment on attachment 8882271 [details]
Bug 1377182 - Fix animation for tabbar session restore button.

https://reviewboard.mozilla.org/r/153348/#review158770
Attachment #8882271 - Flags: review?(gijskruitbosch+bugs) → review+
(Assignee)

Updated

2 years ago
Keywords: checkin-needed

Comment 5

2 years ago
Pushed by ryanvm@gmail.com:
https://hg.mozilla.org/integration/autoland/rev/993e3817d2fe
Fix animation for tabbar session restore button. r=Gijs
Keywords: checkin-needed

Comment 6

2 years ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/993e3817d2fe
Status: NEW → RESOLVED
Last Resolved: 2 years ago
status-firefox56: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 56

Comment 7

a year ago
I have reproduced this bug with Nightly 56.0a1 (2017-06-29) on Windows 8.1 , 64 Bit ! 

This bug's fix is Verified with latest Beta 56.0b12 !

Build   ID    20170914024831
User Agent    Mozilla/5.0 (Windows NT 6.3; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0

[testday-20170915]
You need to log in before you can comment on or make changes to this bug.