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

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; Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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)?; Related issues: (space separated ids); WG Notes: Reply sent to public list thanking for comment Proposal to leave text alone send to member list. Done in 1z; Resolution: RESOLUTION: Add examples to advertising section (popups and popunders) and links to [CENTRAL_MEANING], [LARGE_GRAPHICS] and [POP_UPS]. Proposed Text: For example, some mechanisms that are commonly used for presentation of advertising material (such as pop-ups, pop-unders and large banners) do not work well on small devices and are therefore contrary to Best Practice recommendations such as [CENTRAL_MEANING], [LARGE_GRAPHICS] and [POP_UPS]."; (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; Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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; Related issues: (space separated ids); WG Notes: responded saying that this is more likely to work in the DDC; Resolution: XHTML Basic is more likely to work in the DDC.; (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; Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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?; Related issues: ACTION-329
(space separated ids); WG Notes: Sent reply thanking for input Sent email to group requesting a view. Done in 1z.; Resolution: Change the text: "can be assisted by factors including but not limited to a > consistent style"; (Please make sure the resolution is adapted for public consumption)

substantive comments

Comment LC-1460: Commenter:; Context: Document as a whole; Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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 ?; Related issues: ACTION-330
(space separated ids); WG Notes: Discussed in http://www.w3.org/2006/08/17-bpwg-minutes; needs more data on support of transparency in devices; Resolution: Group resolution (7 sep 2006): wrt LC-1460, we keep gif89a in the ddc and we removenotes on restrictions Done in 1z; (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; Status:
Not assigned; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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,; Related issues: ACTION-332
(space separated ids); WG Notes: Rough consensus from discussion on Aug 17 http://www.w3.org/2006/08/17-bpwg-minutes seems to indicate that we should simply drop this notion of web safe colors from the DDC, since it doesn't impact the Best Practices in any way. Done in 1z; Resolution: We will drop web-safe colors.; (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; Status:
Not assigned; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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,; Related issues: (space separated ids); WG Notes:; Resolution: After having reviewed the state of implementations on the market, the Working Group has agreed to add support for @media rules in the DDC.; (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; Status:
Not assigned; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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.; Related issues: ACTION-331
(space separated ids); WG Notes: done in 1z; Resolution: Respond Point out that commenter misinterpreted what was said, accept that the test can be misinterpreted, reword as "Check that the elements in a style sheet are used in at least one of the pages that reference it" We did not not recommend compression because we determined it was not widely supported.; (Please make sure the resolution is adapted for public consumption)

editorial comments

Comment LC-1461: Commenter: Richard Ishida <ishida@w3.org> (archived message); Context: in (Free standing summary); Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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.; Related issues: ACTION-334
(space separated ids); WG Notes: Responded to Richard Propose to rework the format of the free-standing summary including better document headers Sent request to Richard to review.; Resolution:; (Please make sure the resolution is adapted for public consumption)

Comment LC-1459: Commenter: Frank Ellermann <nobody@xyzzy.claranet.de> (archived message); Context: Document as a whole; Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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 (  in
the table of contents).; Related issues: ACTION-333
(space separated ids); WG Notes: Sean responded with a holding message. Jo followed up and get a response and put a view for the group's consideration.; Resolution: Many thanks for your clarification off-list. The BPWG has reviewed your comments about the apparently broken references and non-breaking space characters. The apparently broken references are caused by the target being specified by an id attribute, rather than an <a name= construction - and it would seem that your browser does not recognise this construction. In view of the document having been produced by a standard XSLT Style sheet that is widely used for other documents from the W3C, it was decided to leave the document as is, in these respects.; (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...; Status:
assigned to Jo Rabin; Type:; Resolution status:
Response drafted Resolution implemented Reply sent to commenter; Response status:
No response from Commenter yet Commenter approved disposition Commenter objected to disposition
Commenter's response (URI):; Comment:
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]; Related issues: (space separated ids); WG Notes: oops, this is an error.; Resolution: Fix in 1z done. Sent reply thanking for pointing this out and noting that it has been attended to.; (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: index.html,v 1.1 2017/08/11 06:44:08 dom Exp $
Please send bug reports and request for enhancements to w3t-sys.org