Bug 953311 - nsIdleService.idl and .cpp comments are still suggesting a "back" notification. r=gsvelto

This commit is contained in:
Marco Bonardo 2014-01-08 18:43:03 +01:00
parent ebbaeb1dde
commit d749e86822
2 changed files with 5 additions and 5 deletions

View File

@ -12,7 +12,7 @@ interface nsIObserver;
* i.e. not used their mouse or keyboard. You can get the idle time directly,
* but in most cases you will want to register an observer for a predefined
* interval. The observer will get an 'idle' notification when the user is idle
* for that interval (or longer), and receive a 'back' notification when the
* for that interval (or longer), and receive an 'active' notification when the
* user starts using their computer again.
*/
@ -40,8 +40,8 @@ interface nsIIdleService : nsISupports
* @note
* The subject of the notification the observer will get is always the
* nsIIdleService itself.
* When the user goes idle, the observer topic is "idle" and when they get
* back, the observer topic is "back".
* When the user goes idle, the observer topic is "idle" and when he gets
* back, the observer topic is "active".
* The data param for the notification contains the current user idle time.
*
* @note

View File

@ -578,8 +578,8 @@ nsIdleService::ResetIdleTimeOut(uint32_t idleDeltaInMS)
return NS_OK;
}
// Now send "back" events to all, if any should have timed out allready, then
// they will be reawaken by the timer that is already running.
// Now send "active" events to all, if any should have timed out already,
// then they will be reawaken by the timer that is already running.
// We need a text string to send with any state change events.
nsAutoString timeStr;