ACTION-401: Larry as Lo-Fi prototype for 6.1.1

Mez asked in IRC today if I would consider Firefox 3 to be an example  
of an implementation of the identity signal outlined in section 6.1.1,  
and if so, would I screencap it and show how it fulfills the  
requirements there.

The text of the section is:

-- SNIP --
This section is normative. Examples are informational.

Web user agents MUST make information about the [[identity]] of the  
Web site that a user interacts with available. This [Definition:  
[[identity signal]] ] SHOULD be part of primary user interface during  
usage modes which entail the presence of signalling to the user that  
is different from solely page content. Otherwise, it MUST at least be  
available through secondary user interface. Note that there may be  
usage modes during which this requirement does not apply: For example,  
a Web browser which is interactively switched into a no-chrome, full- 
screen presentation mode need not preserve any security indicators in  
primary user interface.

User interactions to access this identity signal MUST be consistent  
across all Web interactions, including interactions during which the  
Web user agent has no trustworthy information about the [[identity]]  
of the Web site that a user interacts with. In this case, user agents  
SHOULD indicate that no information is available.

User agents with a visual user interface that make the identity signal  
available in primary user interface SHOULD do so in a consistent  
visual position.
-- END --

Here is a screenshot of Firefox 3 beta 4 on Mac, showing the Identity  
UI:

"Web user agents MUST make information about the [[identity]] of the  
Web site that a user interacts with available."

Firefox 3 has a UI element (the "site button") at the left of the  
location bar in primary chrome, which makes identity information  
available.

"This [Definition: [[identity signal]] ] SHOULD be part of primary  
user interface during usage modes which entail the presence of  
signalling to the user that is different from solely page content.  
Otherwise, it MUST at least be available through secondary user  
interface."

The launch point is in primary chrome, not clear if that counts as the  
signal being in primary or secondary, but it complies with the MUST  
and maybe the SHOULD.

"User interactions to access this identity signal MUST be consistent  
across all Web interactions, including interactions during which the  
Web user agent has no trustworthy information about the [[identity]]  
of the Web site that a user interacts with. In this case, user agents  
SHOULD indicate that no information is available."

The site button behaves in this way.  Sites that present no identity  
information display:

"User agents with a visual user interface that make the identity  
signal available in primary user interface SHOULD do so in a  
consistent visual position."

The site button appears in a consistent location, and is available at  
all times (it does not disappear on non-SSL sites like older padlock  
implementations in Firefox).

I believe this meets the requirement, but if people require additional  
details, I recommend http://www.mozilla.com/en-US/firefox/all-beta.html

Cheers,

Johnathan

---
Johnathan Nightingale
Human Shield
johnath@mozilla.com