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

Comments on Mobile Web Application Best Practices

From: Francois Daoust <fd@w3.org>
Date: Tue, 03 Feb 2009 12:20:16 +0100
Message-ID: <49882870.5050103@w3.org>
To: Mobile Web Best Practices Working Group WG <public-bpwg@w3.org>

Hi Adam,

I took a look at the draft commented by Jo:
(and updated latest link to point to it)

I mostly agree with Jo's comments there.
Here are a few additional ones: on Unique URI
  While I understand there are a number of cases where this may be an 
acceptable trade-off, doesn't that trigger a huge privacy issue? Did I 
miss something? Could we refine this part with an example perhaps and a 
strong "be careful!" note?

3.2.1 I'm not so fond of the whole Security and Privacy section, but 
since the Web Security Context Working Group should be getting back to 
us in a short amount of time about it, I leave this comment as a 
placeholder for the time being ;)

3.4.6 The title reads "Minimize External Resources", which overlaps at 
first sight "3.4.2 Minimize application size".
  -> rewrite the title to "Minimize *Number of* External Resources" 
which seems to be the gist of the BP? This does not really explain "how to do it", but rather "how to 
choose when to do it".
  -> Merge the text with
  -> Add a real "how to do it" section, to alert users that we do not 
recommend to mix styles with content via the deprecated "style" 
attribute, but rather to define styles in a "style" element. Similarly, 
we do not recommend to mix Javascript and content via Javascript links 
or events binding on the elements themselves, but via a clean separation 
between content and scripts using the "script" element.

3.4.8 In essence, I understand this BP as applying to images rendered 
via CSS.
  -> Mention CSS somewhere in the title or the "What it means" title? In the focus based section, if selectable elements are "widely 
spaced", couldn't that trigger scrolling problems? (i.e. you jump from 
the top to the bottom of the page, and get lost because the middle of 
the page is skipped?)

3.5.3 I'm not sure I get the meaning of the title and the connection 
with the description of the BP. Shouldn't we be more generic and, 
instead of talking about moving the focus to the part of a page that 
changed, be talking about *alerting" the user that something changed 
(using, e.g. a yellow fade technique)?

Received on Tuesday, 3 February 2009 11:20:50 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:53 UTC