mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
c9ae76ff40
======== https://hg.mozilla.org/integration/gaia-central/rev/4f7140e2e3a9 Author: Fabien Cazenave <fabien@cazenave.cc> Desc: Bug 883822: [SMS] focus the Compose area when started as an activity - r=gnarf When the Compose screen is triggered by an activity (e.g. when clicking on a message icon from the call log), recipients are inserted and the onscreen keyboard is triggered. The problem is, the focus is set within a recipient block, not in the input itself: thus, the onscreen keyboard doesn’t disappear when the back button is hit. A possible fix would have been to focus the recipient input rather than the recipient block, but it’s simpler to focus the Compose area instead (and that’s one less tap for the user). That’s what this simple patch does. Closes gh-10979 ======== https://hg.mozilla.org/integration/gaia-central/rev/6b34842a2150 Author: James Lal <james@lightsofapollo.com> Desc: Merge pull request #11016 from ganesh7/887698 Bug 887698 - [OTA] [Data Migration] [Calendar] Calendar blank screen aft... ======== https://hg.mozilla.org/integration/gaia-central/rev/31a971cb141c Author: gghosh <ganeshghosh@gmail.com> Desc: Bug 887698 - [OTA] [Data Migration] [Calendar] Calendar blank screen after update from v1.0.1 to v1.1.0 |
||
|---|---|---|
| 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/