mirror of
https://gitlab.winehq.org/wine/wine-gecko.git
synced 2024-09-13 09:24:08 -07:00
Gecko engine for Wine
3b150894ff
======== https://hg.mozilla.org/integration/gaia-central/rev/8888606f407e Author: lissyx <lissyx+github@lissyx.dyndns.org> Desc: Merge pull request #26443 from lissyx/bug1103560 Bug 1103560 - [WIP] Unique system message handler for Notifications r=alive,mhenretty,ggp ======== https://hg.mozilla.org/integration/gaia-central/rev/c68a53039840 Author: Alexandre Lissy <lissyx+github@lissyx.dyndns.org> Desc: Bug 1103560 - Unique system message handler for Notifications r=alive,mhenretty,ggp The system message API exposed by Gecko only allows to have one handler per application ; yet, system app do have multiple modules using the Notification API. If those needs to handle the case of notification being resent, then they will need to have a system message handle for the 'notification' message. This is what 'Screenshot' and 'FindMyDevice' did, which means only one could work, depending on which one gets executed. We solve this by introducing a new system service 'handleSystemMessageNotification' that each module should |Service.request| and exposing its module name. Then a 'handleSystemMessageNotification' will get called on the module when a matching system message is being received. We leave the logic of what do to with the notification to the module itself: close it, keep it. |
||
---|---|---|
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 | ||
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/