W3C home > Mailing lists > Public > public-bpwg-comments@w3.org > April to June 2006

Re: Missing points in current last call draft

From: <dom@w3.org>
Date: Wed, 12 Apr 2006 17:05:09 +0000 (GMT)
To: Charles McCathieNevile <chaals@opera.com>
Cc: public-bpwg-comments@w3.org
Message-Id: <20060412170509.737AA66388@dolph.w3.org>

[Sorry for the duplicate]

  Dear Charles McCathieNevile ,

The Mobile Web Best Practice Working Group has reviewed the comments you
sent [1] on the Last Call Working Draft [2] of the Mobile Web Best
Practices 1.0 published on 13 January 2006 Thank you for having taken the
time to review the document and to send us comments!

This message holds the disposition of the said comments on which the
Working Group has agreed. This disposition has been implemented in the new
version of the document available at:
http://www.w3.org/TR/2006/WD-mobile-bp-20060412/

Please review it carefully and let us know if you agree with it or not
before 3 May 2006. In case of disagreement, you are requested to provide a
specific solution for or a path to a consensus with the Working Group. If
such a consensus cannot be achieved, you will be given the opportunity to
raise a formal objection which will then be reviewed by the Director
during the transition of this document to the next stage in the W3C
Recommendation Track.

Thanks,

For the Mobile Web Best Practice Working Group,
Philipp Hoschka
Dominique Hazaƫl-Massieux
W3C Staff Contacts

 1. http://www.w3.org/mid/op.s490dgnhwxe0ny@pc090.coreteam.oslo.opera.com
 2. http://www.w3.org/TR/2006/WD-mobile-bp-20060113/


=====

Your comment on 5.3 Page Content and Layout:
BP Not covered:

1. Don\'t format text as justified.



Text aligned to be justified on both sides is often problematic on the web
 

in general - on mobile devices with a relatively small range of fonts and 


display options, it seriously reduces legibility of content, often at a  

cost of some extra processing.

Working Group Resolution:
We have added a new best practice on text effects:

"[FONTS] Do not rely on support of font related styling."



but we think the particular aspect of justification would be better
handled by a technique that was started at:

http://www.w3.org/2005/MWI/BPWG/techs/TextStyle



----

Your comment on 5.3 Page Content and Layout:
BP Not covered:

2. Identify word breaks.



(This is related to the previous point)



Long words which can be broken should include useful information about  

appropriate points to do so by including a &shy; or similar.

display options, it seriously reduces legibility of content, often at a  

cost of some extra processing.

Working Group Resolution:
We think this would be a better fit for a technique rather than a specific
best practice. A technique has been started in:

http://www.w3.org/2005/MWI/BPWG/techs/TextStyle

----

Your comment on 5.4 Page Definition:
BP Not covered:

3. Use Device-independent event triggers



in HTML, the onmouse* and onkey* triggers are somewhat difficult to  

trigger from the range of devices available. onclick is generally  

implemented in such a way that any device can trigger  it, and mutation  

events (form changes, page load, etc) do not rely on a particular user  

interface anyway.

Working Group Resolution:
We have added the following sentence in the "how to do it" section:

If scripting is used, do not use onmouse and onkey triggers, use onclick.

----

Your comment on 5.4 Page Definition:
BP Not covered:

4. Balance page weight and latency



In a number of cases it will be appropriate to provide a choice between a 


large page and the same page broken into appropriate chunks. (Browsers  

like Opera mini will in any case break a page into appropriate sized  

pieces for phones that need this done).



It can also be important to decide what resources to include externally, 


and which to include in the page. Use of the data: URI scheme can allow  

small images to be included inline (as can SVG where supported by the  

browser), and stylesheets and scripts can likewise be incorporated in the 


page, reducing latency effects caused by fetching multiple resources, or 


linked to allow efficiency from decisions on whether to load them and from
 

caching.

Working Group Resolution:
We agree and have added a new best practice to that effect
(EXTERNAL_RESOURCES), which combined with the BALANCE Best Practice covers
the suggestion.

----
Received on Wednesday, 12 April 2006 17:14:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:01:49 UTC