946
edits
Labs/Weave/Identity/Account Manager/Spec/Latest: Difference between revisions
Jump to navigation
Jump to search
Labs/Weave/Identity/Account Manager/Spec/Latest (view source)
Revision as of 23:34, 8 April 2010
, 8 April 2010→Implementation Considerations
No edit summary |
|||
| Line 231: | Line 231: | ||
= Implementation Considerations = | = Implementation Considerations = | ||
;Embedded Resources | |||
The user-agent MUST NOT take Account Management steps for resources that are embedded in a document. This includes IFRAMEs, scripts, CSS stylesheets, images, and data retrieved by plugins. | The user-agent MUST NOT take Account Management steps for resources that are embedded in a document. This includes IFRAMEs, scripts, CSS stylesheets, images, and data retrieved by plugins. | ||
;Respect for AUTOCOMPLETE=FALSE | |||
It is conventional for websites to indicate that they wish to disable autocompletion of forms by placing the AUTOCOMPLETE attribute with a value of FALSE into the FORM element. | It is conventional for websites to indicate that they wish to disable autocompletion of forms by placing the AUTOCOMPLETE attribute with a value of FALSE into the FORM element. | ||
| Line 241: | Line 241: | ||
User-agents that implement Account Management features SHOULD respect this value as an indication by a website that it wishes not to participate in implementations of this protocol. | User-agents that implement Account Management features SHOULD respect this value as an indication by a website that it wishes not to participate in implementations of this protocol. | ||
;HTTP Basic/Digest Access Authentication | |||
Most common browser implementations of HTTP Access Authentication (RFC 2617) do not include the ability for the user to disconnect (stop sending the Authentication header). Since connect/disconnect are central metaphors to this specification, user agents SHOULD perform an HTTP method call for disconnect if it is so defined (see section 5.2.2). | Most common browser implementations of HTTP Access Authentication (RFC 2617) do not include the ability for the user to disconnect (stop sending the Authentication header). Since connect/disconnect are central metaphors to this specification, user agents SHOULD perform an HTTP method call for disconnect if it is so defined (see section 5.2.2). | ||