mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
802df52b5a
======== https://hg.mozilla.org/integration/gaia-central/rev/d3bf1e5466f0 Author: Fabien Cazenave <fabien@cazenave.cc> Desc: Merge pull request #10943 from fabi1cazenave/mmsAttachmentContainers-bug889899 Bug 889899: use <div> instead of <iframe> for MMS attachment containers, r=julienw ======== https://hg.mozilla.org/integration/gaia-central/rev/662a0765f17a Author: Fabien Cazenave <fabien@cazenave.cc> Desc: Bug 889899: use <div> instead of <iframe> for MMS attachment containers, r=julienw Attachment containers use `<iframe>` in the SMS app because they are handy in the Compose area (work well in a contenteditable element): this ensures that attachment blocks are deletable but not editable. However, `<iframes>` are a pain to use in the message thread, and can become a performance killer on threads with lots of attachments. This patch keeps `<iframe>` containers for draft attachments in the Compose area but relies on `<div>` containers for the message thread. To achieve this we use three templates: * one `attachment-preview` template: - display it in a 80x80 px placeholder (can be extended to 120x80 or 80x120); - display the attachment size if in the Compose window; - do not display the file name for images (another patch will enable to display the file name on video with previews) * one `attachment-nopreview` template: (audio, video, large images) - display the attachment type as a 80x80 px icon (audio, video, image, other); - display the attachment size if in the Compose window; - display the file name, both in the Compose window and in the message thread. * one `attachment-draft` template to embed one of the two previous templates in an `<iframe>` container for the Compose area. Non-draft attachments are displayed in a `<div>` container. In both cases (div or iframe), the container carries an `attachment-container` class and a `preview` or `nopreview` one. Side notes: * this fixes bug 882094 (display attachment file names in MMS); * the `bubbleEvents` method has been slightly re-rewritten to be more self-explanatory; * some basic cleanup has been done on the HTML & CSS front. |
||
|---|---|---|
| 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 | ||
| aclocal.m4 | ||
| Android.mk | ||
| AUTHORS | ||
| client.mk | ||
| client.py | ||
| CLOBBER | ||
| configure.in | ||
| LEGAL | ||
| LICENSE | ||
| mach | ||
| Makefile.in | ||
| 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/