W3C home > Mailing lists > Public > public-wsc-wg@w3.org > May 2008

RE: ISSUE-206 (Smartphones): Proposed changes/additions [wsc-xit]

From: Luis Barriga <luis.barriga@ericsson.com>
Date: Wed, 14 May 2008 14:10:28 +0200
Message-ID: <1C6A13C92F510849B72272A71F9F3BCB0384DBFF@esealmw105.eemea.ericsson.se>
To: "Web Security Context Working Group WG" <public-wsc-wg@w3.org>

Here is a list of tentative changes/additions to make the current and
upcoming draft address smartphone aspects. Note I'm not addressing the
whole range of handled devices which is a larger issue to work on. I
just feel we need to start somewhere.

** Change 4.2.1, 3rd paragraph:
"Examples of primary user interface include the location bar in common
desktop Web user agents, the "padlock" icon present in common desktop
Web user agents, or error pages that take the place of a Web page that
could not be retrieved."
to
"Examples of primary user interface include the location bar in common
desktop/smartphone Web user agents, the "padlock" icon present in common
desktop/smartphone Web user agents, or error pages that take the place
of a Web page that could not be retrieved."

** Change 4.2.1, 5th paragraph:
"Examples of secondary user interface include the "Page Information"
dialogue commonly found in desktop Web user agents, and the "Security
Properties" dialogue that can obtained by clicking the padlock icon in
common desktop Web user agents."
to
"Examples of secondary user interface include the "Page Information"
dialogue commonly found in desktop/smartphone Web user agents, and the
"Security Properties" dialogue that can obtained by clicking the padlock
icon in common desktop or touchscreen smartphone Web user agents."

** Change 5.1.1, 2nd paragraph:
"Trust anchor installation is typically handled by Web user agent
vendors and systems administrators, based on out-of-band information.
Note that trust anchor update is therefore often handled as part of Web
user agent or operating system software update."
to
"Trust anchor installation is typically handled by Web user agent
vendors, smartphone manufacturers and systems administrators, based on
out-of-band information. Note that trust anchor update is therefore
often handled as part of Web user agent or operating system software
update."

** Add to the end of 6.1.1 2nd paragraph & 6.3 1st paragraph:
"... However, a smartphone browser which is interactively switched into
a full-screen mode has to preserve any security indicators in primary
user interface if these were previously available.

** Change 7.2 1st paragraph:
"For example, the location bar commonly found on desktop browsers is
often used to both display the "padlock" security indicator, and a
possible "favorite icon" [FAVICON], which can in turn be a simple copy
of the very padlock an informed and attentive user might look for."
to
"For example, the location bar commonly found on desktop browsers or the
status bar in smartphones are often used to both display the "padlock"
security indicator, and a possible "favorite icon" [FAVICON], which can
in turn be a simple copy of the very padlock an informed and attentive
user might look for."

** Change upcoming result to ACTION 433:
"For visual user agents, browser chrome SHOULD always be present to
signal security context information. This requirement does not apply
when UI is explicitly dismissed by the user, e.g. by switching to full
screen mode."
to
"For visual user agents, browser chrome SHOULD always be present to
signal security context information. This requirement does not apply
when UI is explicitly dismissed by the user, e.g. by switching to
presentation mode in desktops. However, it does apply when user switches
to full-screen mode in smartphones."
Received on Wednesday, 14 May 2008 12:11:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 14 May 2008 12:11:13 GMT