Open Bug 1485554 Opened 1 year ago Updated 1 year ago
Some arrow panels have no opening animation
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0 Build ID: 20180822221004 Steps to reproduce: Open Nightly Open arrow panels Actual results: They open without animation. Expected results: They animate open. Testing with the built in arrow panels, this issue affects history, text encoding, forget, developer, library, all tabs list, save to pocket, and send tab to device. It does not affect the main menu, bookmarks menu, download panel, control center, page actions menu, and bookmark this page.
It seems to be related to the startupCache.8.little file in the startupCache folder. Deleting this file fixes the opening animation for the next launch, but the one after that is broken again.
Running mozregression I got: 2018-08-24T15:24:46: DEBUG : Using url: https://hg.mozilla.org/integration/mozilla-inbound/json-pushes?changeset=2e8624a457a61ad282e163741c7b1fad91df4434&full=1 2018-08-24T15:24:47: DEBUG : Found commit message: Bug 1461793 - Remove the "popup-base" binding and import the "popup.css" file as a document stylesheet. r=bgrins The new "tooltip.css" file allows styling the default tooltip, which is created as native anonymous content. MozReview-Commit-ID: ADWsFTNPfhw
Component: Untriaged → XUL Widgets
Product: Firefox → Toolkit
Summary: Some arrow panels randomly have their opening animation break → Some arrow panels have no opening animation
Neil could you prioritize this regression? Can we wontfix it for 63? Thanks
Paolo, there is a suggestion that this is a regression from 1461793 that would be good to look at. Seems like it would be a noticeable issue, but we haven't got any other reports of this.
Priority: -- → P2
I suspect this may be related to the issue for which bug 1470880 is on file, which only happened during automated tests.
See Also: → 1470880
Spoke with mconley and determined that these are not active right now. As P2 and small impact, we've set wontfix for 63.
You need to log in before you can comment on or make changes to this bug.