mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
db77d0630f
======== https://hg.mozilla.org/integration/gaia-central/rev/84dbd52b4ab1 Author: You-Sheng Yang <vicamo@gmail.com> Desc: Merge pull request #17380 from vicamo/bugzilla/936703/call-screen-indexeddb-abort-error Bugzilla/936703/call screen indexeddb abort error ======== https://hg.mozilla.org/integration/gaia-central/rev/8e5cbba30fed Author: You-Sheng Yang <vicamo@gmail.com> Desc: Bug 936703 - [async_storage] callback in transaction.oncomplete event. r=djf CostControl app invokes |Common.closeApplication()| in its asyncStorage operation callbacks. However, these callbacks are invoked in IDBRequest.onsuccess events when the corresponding transaction is not necessarily completed. That is, we may have following sequence: 1) IDBRequest.onsuccess 2) call to Common.closeApplication() 3) invalidate open IDBDatabase 4) trying to invoke IDBTransaction.oncomplete results in an AbortError. We should follow W3C's suggestion here -- listen IDBTransaction.oncomplete instead of IDBRequest.onsuccess. [1]: http://www.w3.org/TR/IndexedDB/#widl-IDBTransaction-oncomplete |
||
---|---|---|
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 | ||
.clang-format | ||
.clang-format-ignore | ||
.gdbinit | ||
.gitignore | ||
.hgignore | ||
.hgtags | ||
.lldbinit | ||
.reviewboardrc | ||
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/