Created attachment 8831439 [details] Unsmooth WhatsApp Web emoji selector (2017-01-28 build) User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:54.0) Gecko/20100101 Firefox/54.0 Build ID: 20170128030204 Steps to reproduce: (Please refer to the attached video.) 0. Have a WhatsApp account. 1. Log in to https://web.whatsapp.com/. 2. In the chat window, click the emoji selector so it slides out. Actual results: The transition is not smooth. Note: Same as bug 1334715, the bug does not appear in non-e10s mode.
Created attachment 8831441 [details] Expected result (2017-01-25 build) From mozregression: Last good Nightly: 2017-01-25 First bad Nightly: 2017-01-26 https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6dccae211ae5fec6a1c1244b878ce0b93860154f&tochange=fbdfcecf0c774d2221f11aed5a504d5591c774e0 Further bisection: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=f0248c53cef751d0eed4c9d1979d69f32dc5c617&tochange=44f9535628fd46d78fe020a8175bedc5f8b98680 Regressed by bug 1332567
This is actually unbearably slow for me on two builds I tried before that changeset: Firefox 52 beta, and the Nightly from 1/23. But, I tried selecting an emoji from the "Create Group" window instead of a chat window. Does the "Create Group" window exhibit the same behavior for you? (Slow before, and slow after, that changeset?)
Flags: needinfo?(dvander) → needinfo?(Fanolian+bugzilla)
(In reply to David Anderson [:dvander] from comment #2) > This is actually unbearably slow for me on two builds I tried before that > changeset: Firefox 52 beta, and the Nightly from 1/23. But, I tried > selecting an emoji from the "Create Group" window instead of a chat window. > > Does the "Create Group" window exhibit the same behavior for you? (Slow > before, and slow after, that changeset?) No, the emoji selector in "Create Group" window is smooth for me, before or after the changeset.
status-firefox51: --- → unaffected
status-firefox52: --- → unaffected
status-firefox53: --- → unaffected
status-firefox54: --- → affected
I can no longer reproduce this bug in 2017-02-01 build. It's probably fixed by bug 1334715.
Status: UNCONFIRMED → RESOLVED
Last Resolved: a year ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1334715
Since 54 was fixed in bug 1334715, mark 54 fixed.
status-firefox54: affected → fixed
You need to log in before you can comment on or make changes to this bug.