W3C home > Mailing lists > Public > public-bpwg@w3.org > February 2009

Re: [ACTION-908] good practice for login forms

From: Francois Daoust <fd@w3.org>
Date: Wed, 04 Feb 2009 18:51:05 +0100
Message-ID: <4989D589.4060109@w3.org>
To: Luca Passani <passani@eunet.no>
CC: public-bpwg@w3.org

Luca Passani wrote:
> 
> Francois Daoust wrote:
>>
>> Luca Passani wrote:
>>>
>>>
>>>>  However, I find it reasonable to believe that future browsers
>>>>  will provide.....
>>>  ^^^^
>>>
>>>
>>> Still stuck with the famous "forward-looking best practices"....
>>
>> Most of the best practices in the Mobile Web Application Best 
>> Practices document target more advanced browsers, so it sounds 
>> reasonable to put "future" on the table when considering a potential 
>> new best practice, especially if the BP in question might create a 
>> future problem. I understand this led to endless debates in the past, 
>> but don't quite see why it applies here.
>>
> I think you are mistaken.
> 
> http://www.w3.org/TR/mobile-bp/#ddc

Sure, but we're not talking about a BP for the Mobile Web Best Practices 
(MWBP) recommendation here. We're talking about a BP for the Mobile Web 
Application Best Practices (MWABP) draft.

There is no DDC in MWABP. See section 1.3.4:
 
http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090101#d1e256

The goal of these additional best practices is to exploit devices 
capabilities when you know about them. For instance, many of the best 
practices only apply when the mobile device has support for scripting, 
and thus do not target DDC-like devices.

Francois.


> 
> Best practices has the concept of Default Delivery Context, i.e. minimal 
> set of features which guarantees that a mobileOK will be displayed 
> correctly. These properties characterize your typical feature phone:
> 
> ---------------------------
> Usable Screen Width
> 
> 120 pixels, minimum.
> Markup Language Support
> 
> XHTML Basic 1.1 [XHTML-Basic] delivered with content type 
> application/xhtml+xml.
> Character Encoding
> 
> UTF-8 [UTF-8].
> Image Format Support
> 
> JPEG.
> 
> GIF 89a.
> Maximum Total Page Weight
> 
> 20 kilobytes.
> Colors
> 
> 256 Colors, minimum.
> Style Sheet Support
> 
> CSS Level 1 [CSS]. In addition, CSS Level 2 [CSS2] @media rule together 
> with the handheld and all media types (see CSS 2 Media Types).
> HTTP
> 
> HTTP/1.0 [HTTP1.0] or more recent [HTTP1.1].
> Script
> 
> No support for client side scripting.
> ----------
> 
> Again: a MobileOK page is supposed to work on a device with these 
> minimal features.
> 
> Luca
> 
> 
> 
> 
Received on Wednesday, 4 February 2009 17:51:39 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:00 UTC