Re: ISSUE-206 (Smartphones): Smartphone Considerations [wsc-xit]

Web Security Context Working Group Issue Tracker wrote:
> ISSUE-206 (Smartphones): Smartphone Considerations [wsc-xit]
>
> http://www.w3.org/2006/WSC/track/issues/
>
> Raised by: Luis Barriga
> On product: wsc-xit
>
> Current draft is desktop oriented. Some sections can be modified to
> consider smartphone scenarios.

I think we can adopt an even broader scope of small screen devices, such as 
audio/video players, hand held game consoles, or even TV-based user agents 
which have a very low screen resolution compared to typical desktop computer 
screens.

> For example, full-screen is often assumed to be no-chrome which is common
> in desktop presentation mode, but not when a mobile user browses in her
> smartphone in full-screen due to small screen limitation and chrome could
> be still needed.
>
> Also, yesterday anew text was proposed stating (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."

I see a trend in user interfaces, that by using animated UI elements, or even 
semi-transparent elements which act very responsively for the user. This 
blurs the line between what is primary and secondary user interface. The spec 
currently has a very clear distinction of these two.

I think primary user interface not necessarily need to be on-screen in it's 
entirety. I think the primary user interface definition is a bit too 
restrictive in these cases.


-- 
Jan Vidar Krey
Unix Software Engineer
B2B Chief Security Officer

Opera Software ASA
tel: +47 24164287 (work) / +47 98607328 (mobile)

<Endy> knghtbrd: QW's netcode is doing strange things to me. :P
<knghtbrd> This is unusual?  ;>
<Endy> Not really. :P

Received on Wednesday, 14 May 2008 11:51:10 UTC