ISSUE-241
TLS indicator in primary chrome
- State:
- CLOSED
- Product:
- wsc-xit
- Raised by:
- Thomas Roessler
- Opened on:
- 2010-02-22
- Description:
- The CR version of this specification provided the possibility for the TLS indicator to be present in secondary chrome. None of the implementations make use of this option; all have it in primary chrome. All implementations also have a blank TLS indicator in the case of a usual HTTP connection.
To match implemented behavior, proposed to change the first two paragraphs of 6.3 into:
User agents MUST make information about the state of TLS protection available. The [Definition: TLS indicator] MUST be part of primary user interface during usage modes which entail the presence of signaling to the user beyond only presenting page content. As in the case of 6.1.1 Identity Signal, there may be usage modes during which this requirement does not apply. Web content MUST NOT obscure security interface, 7.4.1 Obscuring or disabling Security User Interfaces.
User agents with a visual user interface SHOULD make the TLS indicator available in a consistent visual position.
- Related Actions Items:
- No related actions
- Related emails:
- Re: ISSUE-241: TLS indicator in primary chrome [wsc-xit] (from mzurko@us.ibm.com on 2010-02-26)
- Re: Agenda: WSC WG distributed meeting, Wednesday, 2010-02-24 (from tlr@w3.org on 2010-02-23)
- ISSUE-241: TLS indicator in primary chrome [wsc-xit] (from sysbot+tracker@w3.org on 2010-02-22)
Related notes:
No additional notes.
Display change log
