зеркало из https://github.com/mozilla/gecko-dev.git
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
7ac4e3a007
======== https://hg.mozilla.org/integration/gaia-central/rev/98bed50f82ab Author: Mike Pennisi <mike@mikepennisi.com> Desc: Bug 905273 - [Messages] Recipients list pull down animation is inefficient r=julienw In order to use the more efficient `transform` attribute for animating the pull-down, the element responsibilities must be altered. The top-level "#messages-to-field" serves as a basis for positioning the "#to-label" and "#messages-contact-pick-button". It is no longer animated, and because of this, it no longer draws the component's background or border. A new element, "#messages-recipients-list-container" has been introduced to take the responsibilities previously fulfilled by the "#messages-to-field". Animation is implemented via the `transform` attribute. In order to prevent unecessarily scrolling in "multiline" mode, the rendering of the recipients has been simplified. The JavaScript `generateHeightRule` function no longer has to reset the height of the widget: all elements are now rendered at full height. The method has been simplified to simply set the "#message-recipients-list" element's `max-height` in order to trigger the rendering of a scroll bar when the number of recipients causes overflow in multi-line mode. |
||
|---|---|---|
| accessible | ||
| addon-sdk | ||
| b2g | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| content | ||
| db/sqlite3 | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| hal | ||
| image | ||
| intl | ||
| ipc | ||
| js | ||
| layout | ||
| media | ||
| memory | ||
| mfbt | ||
| mobile | ||
| modules | ||
| mozglue | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| profile | ||
| python | ||
| rdf | ||
| security | ||
| services | ||
| startupcache | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webapprt | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xulrunner | ||
| .gdbinit | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| AUTHORS | ||
| Android.mk | ||
| CLOBBER | ||
| LEGAL | ||
| LICENSE | ||
| Makefile.in | ||
| README.txt | ||
| aclocal.m4 | ||
| client.mk | ||
| client.py | ||
| configure.in | ||
| mach | ||
| moz.build | ||
| mozilla-config.h.in | ||
README.txt
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:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/