Closed Bug 847352 Opened 12 years ago Closed 12 years ago

Preload SystemMessageHandler.js

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: vingtetun, Assigned: vingtetun)

References

Details

(Whiteboard: [FFOS_perf][fixed-in-birch])

Attachments

(1 file)

Attached patch PatchSplinter Review
SystemMessageHandler.js is used by most of the core apps and this is hard to move it out of the main startup path since this is a reasonable place for navigator.setMessageHandler to be called. Initializing the service at startup can be avoided like we do for SettingsManager.js
Attachment #720633 - Flags: review?(fabrice)
Comment on attachment 720633 [details] [diff] [review] Patch Review of attachment 720633 [details] [diff] [review]: ----------------------------------------------------------------- r=me with nit addressed ::: dom/ipc/preload.js @@ +78,5 @@ > Cc["@mozilla.org/contentsecuritypolicy;1"].createInstance(Ci["nsIContentSecurityPolicy"]); > > /* Applications Specific Helper */ > Cc["@mozilla.org/settingsManager;1"].getService(Ci["nsIDOMSettingsManager"]); > + Cc["@mozilla.org/system-message-manager;1"].getService(Ci["nsIDOMNavigatorSystemMessages"]); That needs to be guarded by #ifdef MOZ_SYS_MSG
Attachment #720633 - Flags: review?(fabrice) → review+
Status: NEW → ASSIGNED
OS: Linux → All
Hardware: x86_64 → All
(In reply to Vivien Nicolas (:vingtetun) (:21) from comment #2) > https://hg.mozilla.org/integration/mozilla-inbound/rev/6c2e3ea6afa6 Reminder, B2G work should be landing on birch, not inbound. Also, the reason for the backout was for mass test bustage. Please run your patches through Try before re-landing.
Whiteboard: [FFOS_perf] → [FFOS_perf][fixed-in-birch]
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: