mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-28 21:28:55 +00:00

By default RecyclerView assumes any item change *might* need animation. It then creates a new copy of the item that has changed, and interpolates between the two to "animate" the change. We don't need that for topsites (the RecyclerView's we use inside each TopSitePanel already animate changes, the overall size doesn't change - moreover ViewPager state gets lost if you create a new panel), so we override this behaviour to retain the existing panel. This stops the previously visible horrible flickering. (Every time history changes, which can happen if sync is working, or even if a page finishes loading in the background, the DB is changed, and a reload is triggered. Prior to this commit, topsites would flicker horribly, and would reset back to the first topsites page. After this commit the page is retained, and the visible topsites are rearranged by the inner RecyclerView's animations. You can test this by pinning a site on the first page, the pinned site will shift to the front, the other sites smoothly move to the right.) MozReview-Commit-ID: CnocNfdQ2FS --HG-- extra : rebase_source : 3a4e1d86c786126aee1e08ab020b855056e4f921
…
…
…
…
servo: Merge #15594 - Fix initial value of align-content and justify-content (from mbrubeck:align-content-fix); r=Manishearth
Bug 1338776 - Support GetContentsScaleFactor and GetDefaultCSSScaleFactor in ScreenProxy. r=jfkthame
Bug 1328066 - Don't broadcast the live-resize events to all browser windows unnecessarily. r=mstange
…
…
…
…
…
…
…
…
An explanation of the Mozilla Source Code Directory Structure and links to project pages with documentation can be found at: https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure For information on how to build Mozilla from the source code, see: http://developer.mozilla.org/en/docs/Build_Documentation To have your bug fix / feature added to Mozilla, you should create a patch and submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at: http://developer.mozilla.org/en/docs/Creating_a_patch http://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree If you have a question about developing Mozilla, and can't find the solution on http://developer.mozilla.org, you can try asking your question in a mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups are accessible on Google Groups, or news.mozilla.org with a NNTP reader.] You can download nightly development builds from the Mozilla FTP server. Keep in mind that nightly builds, which are used by Mozilla developers for testing, may be buggy. Firefox nightlies, for example, can be found at: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ - or - http://nightly.mozilla.org/
Description
Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
Languages
JavaScript
32.3%
C++
25.4%
HTML
21.1%
C
10.8%
Python
2.8%
Other
7.1%