Confirmed users
134
edits
Identity/Verified Email Protocol/Session API: Difference between revisions
Identity/Verified Email Protocol/Session API (view source)
Revision as of 23:07, 27 July 2011
, 27 July 2011Starting to add examples, expand on the binding.
Stomlinson (talk | contribs) (Starting to add examples, expand on the binding.) |
Stomlinson (talk | contribs) (Starting to add examples, expand on the binding.) |
||
| Line 85: | Line 85: | ||
Once a site declares session information, it must have session information available on every page within the domain to avoid status flicker. The session information is searched for in the following order: | Once a site declares session information, it must have session information available on every page within the domain to avoid status flicker. The session information is searched for in the following order: | ||
* navigator.id.sessions | |||
* if navigator.id.sessions is undefined, in the binding information for the domain. | |||
If neither are available, the browser will assume both that the session information has expired and the page does not support the session API - it will remove the session status indicator. | If neither are available, the browser will assume both that the session information has expired and the page does not support the session API - it will remove the session status indicator. | ||