W3C

List of comments on “Mobile Web Best Practices 1.0” (dated 27 June 2006)

Quick access to

There are 10 comments (sorted by their types, and the section they are about).

question comments

Comment LC-1484: Spell out Advertising Mechanisms
Commenter: Owen ONeill <Owen.ONeill@eworks.edu.au> (archived message)
Context: 2.5 Advertising
assigned to Jo Rabin
Resolution status:

2.5 Advertising

"...For example, some mechanisms that are commonly used for presentation
of advertising material do not work well on small devices and are
therefore contrary to the Best Practice recommendations."

This sentence specifies "some mechanisms". Are these mechanisms listed
anywhere (not necessarily in the document)?
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1462
Commenter: R. Mengis <mail@1info.com>
Context: 3.7 Default Delivery Context
assigned to Jo Rabin
Resolution status:

Why use recomendation Xhtml Basic Only?
Test this web site resize your windows screen to size (Witdh / Height ) to your PC or any Mobile phone or any Palm.
http://www.1computer.info/1work_demo_en.html
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

general comment comments

Comment LC-1483
Commenter: Owen ONeill <Owen.ONeill@eworks.edu.au> (archived message)
Context: 2.1 Presentation Issues
assigned to Jo Rabin
Resolution status:

2.1 Presentation Issues

"It is particularly important in the mobile context to help the user
create a mental image of the site. This can be assisted by adopting a
consistent style and can be considerably diminished by an uneven style."

Consistent style isn't the only way to achieve this - what about other
aspects such as logical navigation?
ACTION-329
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

substantive comments

Comment LC-1460
Commenter:
Context: Document as a whole
assigned to Jo Rabin
Resolution status:

In section 3.7 (default delivery context) you allow JPEG and
GIF 89a (non-interlaced, non-transparent, non-animated). The
latter would be almost the same as GIF 87a adding text chunks.
What is a mobile device supposed to do with text in GIF 89a ?
Or in other words, what's wrong with the transparency concept
in GIF 89a ?
ACTION-330
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1458
Commenter: Susan Lesch <slesch@w3.org> (archived message)
Context: 3.7 Default Delivery Context
Not assigned
Resolution status:

Hello,

A comment for the MWBP guidelines 3.7 Default Delivery Context [1]. Under
Colors it says:

"Web safe.

(A Web safe color is one that has Red/Green/Blue components
chosen only from the values 0, 51, 102, 153, 204, and 255.)"

The definition looks good but usage of the phrase "Web safe" doesn't always
match the definition. Maybe the spec could say "216 colors" instead of Web
safe (the 216 are the 6x6x6 cube that is part of some popular 8-bit video
palettes). Chris Lilley, copied on this mail, may or may not have a moment to
correct me there.

[1] http://www.w3.org/TR/2006/CR-mobile-bp-20060627/#ddc

Thank you,
ACTION-332
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1523
Commenter: Susan Lesch <slesch@w3.org> (archived message)
Context: 3.7 Default Delivery Context
Not assigned
Resolution status:

Hello,

A comment for the MWBP guidelines 3.7 Default Delivery Context [1]. Under
Style Sheet Support it says:

"External CSS Level 1"

Can the DDC include the handheld media type from CSS2? It is a W3C
Recommendation since 1998 [2,3]. Section 3.5 of the guidelines mentions the
finer-grained CSS Media Queries but I believe they are not yet a
Recommendation. I apologize for sending this comment at this late date but it
strikes me as important enough to ask that users of the MWBP which are devoted
for the most part to handheld devices be able to use the handheld CSS standard.

[1] http://www.w3.org/TR/2006/CR-mobile-bp-20060627/#ddc
[2] http://www.w3.org/TR/1998/REC-CSS2-19980512/
[3] http://www.w3.org/TR/1998/REC-CSS2-19980512/media.html#media-types

Thank you,
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1463
Commenter: Anne van Kesteren <annevk@opera.com> (archived message)
Context: 5.4.9.3 What to test
Not assigned
Resolution status:

The third point
http://www.w3.org/TR/2006/WD-mobile-bp-20060518/#iddiv473140712
STYLE_SHEETS_SIZE does not seem like a good test to me. One of the ideas
of style sheets is that they are cached and can be reused on other sites
within the same website. This sometimes (or often, perhaps) leads to some
rules in the style sheet not being applicable to every page within a site.

If you really want to improve the size of style sheets you might want to
recommend gzip or similar compression mechanism. I'm unsure about support
for that on mobile devices in general though.

Anyway, I'd suggest removing or rewording that test suggestion.
ACTION-331
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

editorial comments

Comment LC-1459
Commenter: Frank Ellermann <nobody@xyzzy.claranet.de> (archived message)
Context: Document as a whole
assigned to Jo Rabin
Resolution status:

could you please "downgrade" this document to be visible
with "any" browser ? Some internal links apparently have no
anchors, or their anchors have no name=, I didn't check the
source. I'd also appreciate it if you replace the three used
non-ASCII characters by NCRs or symbolic references (&nbsp; in
the table of contents).
ACTION-333
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1461
Commenter: Richard Ishida <ishida@w3.org> (archived message)
Context: in (Free standing summary)
assigned to Jo Rabin
Resolution status:

I feel the presentation of the free-standing summary of statements could be improved.

I find the text on the blue/green background much harder to read than the blue text on white background. For people scanning, that is exactly the wrong way around, I think. In fact, even when trying to read in detail, I keep finding my eye pulled away from the actual statements to the - what are those, anyway?

I would be inclined to make this into a proper list <ol>, remove the background highlight, or at least significantly lighten it, make the text itself the link, and move the capitalized text to the end of the list item. Also, add a (v brief) description of what the capitalized stuff is to the page.
ACTION-334
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Comment LC-1457
Commenter: Alejandro Gonzalo Bravo Garc <alejandrogbravo@yahoo.es> (archived message)
Context: [VALID_MARKUP] Create documents that val...
assigned to Jo Rabin
Resolution status:

There is a broken link in the "Mobile Web Best Practices 1.0". In the code source, we can see now "[p]This relates to WCAG [a href=""]3.2[/a]" (obiously, we have to replace "][" with "><").

The anchor will be
[p]This relates to WCAG [a href="http://www.w3.org/TR/WAI-WEBCONTENT/#tech-identify-grammar"]3.2[/a]
(space separated ids)
(Please make sure the resolution is adapted for public consumption)

Add a comment.


Developed and maintained by Dominique Hazaël-Massieux (dom@w3.org).
$Id: Overview.php,v 1.46 2013-10-04 08:11:33 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org