canmove, Confirmed users
2,056
edits
Site-Specific Preferences: Difference between revisions
→Controller
| Line 256: | Line 256: | ||
For location changes, the controller calls nsIObserver::observe with: | For location changes, the controller calls nsIObserver::observe with: | ||
* | * aSubject: the URI of the new location; | ||
* | * aTopic: "content-pref-location-changed"; | ||
* | * aData: the value of the site-specific preference for the new location. | ||
For DOMContentLoaded events, the controller calls nsIObserver::observe with: | For DOMContentLoaded events, the controller calls nsIObserver::observe with: | ||
* | * aSubject: the document object whose content was loaded; | ||
* | * aTopic: "content-pref-dom-content-loaded"; | ||
* | * aData: the value of the site-specific preference for the document. | ||
Note: this doesn't actually conform to the nsIObserver interface, in which | Note: this doesn't actually conform to the nsIObserver interface, in which aData is a wstring, so it will only work with pref handlers implemented in JavaScript and registered without going through XPCOM. | ||
<strong>Should we define an nsIObserver2 interface in which | <strong>Should we define an nsIObserver2 interface in which aData is an nsIVariant?</strong> | ||
<strong>Are these the right topic names for these notifications?</strong> | <strong>Are these the right topic names for these notifications?</strong> | ||
<strong>Should | <strong>Should aSubject be the event object rather than the document object for DOMContentLoaded notifications?</strong> | ||
<strong>Will any pref handlers want to know about pageshow/hide?</strong> | |||
== Text Zoom Handler == | == Text Zoom Handler == | ||