gecko-dev/dom/settings
Alexandre Lissy 127bb2dc72 Bug 1092384 - Use undefined windowID for service locks r=bent
Service locks for settings are locks created from chrome code and not
attached to any window. Since the windowID is used in other cases for
the Settings:CreateLock message, we should at least pass an undefined
value to avoid unneccessary JS warning.
2014-11-04 15:08:37 -08:00
..
tests Bug 1076597 - Fix Settings API shutdown race condition. r=bent 2014-10-09 05:12:00 -04:00
moz.build Bug 1076597 - Fix Settings API shutdown race condition. r=bent 2014-10-09 05:12:00 -04:00
SettingsDB.jsm Bug 1047483 - patch 1 - Porting DOMFile/DOMBlob to WebIDL, r=bz, r=bkelly, r=bholley 2014-10-08 17:15:22 +01:00
SettingsManager.js Bug 1082001 - Cleanup settings lock from parent itself. r=bent 2014-10-29 02:36:00 -04:00
SettingsManager.manifest Bug 889503 - Move Settings API to WebIDL. r=gwagner r=bz 2013-07-15 18:17:46 -07:00
SettingsRequestManager.jsm Bug 1082001 - Cleanup settings lock from parent itself. r=bent 2014-10-29 02:36:00 -04:00
SettingsService.js Bug 1092384 - Use undefined windowID for service locks r=bent 2014-11-04 15:08:37 -08:00
SettingsService.manifest Bug 788561 - SettingsAPI: Use createLock instead of getLock. r=bent 2012-09-05 17:33:03 -07:00