This document:Public document·Annotated document·View comments·Search comments·Add a new comment·Send replies to comments·Disposition of Comments·
Nearby:Mobile Web Best Practices Working Group
Other specs in this tool
Mobile Web Best Practices Working Group's Issue tracker
Quick access to LC-2265
There are 31 comments (sorted by their types, and the section they are about).
Re Status of the Document (SotD) section: given this document is
purely non-normative, why is this document "expected to become a W3C
Recommendation" rather than a Working Group note? For example, how
would this document ever be able to meet the following entrance
criteria for Proposed Recommendation:
2. Shown that each feature of the technical report has been implemented.
nit: double period at the end of first sentence
Cookies being disabled by devices isn't a mobile specific issue as it
also applies to desktop. New devices Android, iPhone, Nokia s60 and
beyond, Palm, etc.. all ship with cookies enabled by default.
Maybe it is covered elsewhere but there is no mention of privacy
issues sending data back to the server via cookies, only the network
concern. With access to very sensitive data like location this might
be worth flagging for mobile.
This is a dangerous recommendation when even modern browsers like
mobile safari on iPhone have a limited browser cache entry size of
25kb uncompressed. It is a good recommendation but relies partially on
the assumption that the caching of a single large resource is no worse
than multiple single resources.
1.3.2: "Web Widgets Effort" that would be the "W3C Widgets effort", or perhaps the "W3C Widgets family of specifications" (as WebApps call them).
1.5: "The implicit reference to XML suggested by the names is commonly accepted to be an historical anomaly." It's historical for sure, but it's not really an anomaly: it really corresponded to what people were thinking of at the time.
188.8.131.52: Storage has been split from HTML5, and there are several parallel local storage efforts in WebApps. In general it would be good to be more precise: "BONDI [BONDI], HTML5 [HTML5], and Opera Widgets [OPERA]" isn't very helpful. For instance, are you thinking of the BONDI address book interface? Or the file system interface? The calendar API? They can all store local data.
Given that HTML5 is now drafting specs for a Web Storage and Web
Database that is shipping in iPhone 3.x and Android 2.x it seems odd
to me to mention Bondi and Opera widgets in this context, especially
given the focus of this document is for applications in a browser.
The second point of "making updates locally at first" should be
supplemented with a need to add UI treatment to make it clear to the
user that their data is uncommitted.
184.108.40.206: Note that some browsers now ship with native JSON parsing.
One way to be able to eval() untrusted data is to perform the JSON
escaping on the server where the processing power is less constrained
than on the client since we are downloading the data anyway
3.3: "Browsers may have access to information such as: â€¢ Pictures, music, and video clips; â€¢ Contacts, calendar (PIM data); â€¢ Call history; â€¢ System data (battery, coverage, roaming, location); â€¢ Media recording (record audio/video clip, get new picture); â€¢ Device context (e.g. location, connectivity, profile setting)."
I am not aware that there are any plans to grant browsers access to such information gratuitously. They may be granted within web runtimes, but even then with clear restrictions. In general this seems to address implementers more than authors.
3.3.1: Also seems to be more for implementers than authors. This information should be provided in a consistent manner by the UI, not the app. The BP I expected here is the one in 3.3.2.
AFAIK some devices will provide UI indications in their status bar of
network activity, with a spinner or mobile data flow indicators. While
informing users of background network usage may be desirable, it might
be overkill to have 3 separate indicators. Maybe you could suggest to
provide UI on devices where the browser does not do it natively
"must" seems a bit strong here. Some applications that inherently
require network access (think IM, mapping, etc..) will not be usable
with no network access, so providing such an option should not be
3.3.3: Again, implementer-orientated. I think that it would be more useful to have separate documents for authors and implementers. Also, the notion that putting notices about usage of a user's personal information in help pages implements a best practice is somewhat dubious. It's hard to find users accessing help pages on a desktop, I don't believe anyone ever does on a mobile (in fact, I'm not sure where I'd find such things).
Consider adding something along the lines of
"If devices persist authentication tokens then the server MUST
invalidate them if the user changes or resets their password"
This is especially important with mobile devices that are often
lost/stolen and provides a user with a way to after the fact lock the
phone out of web applications it had previously been authorised for.
220.127.116.11 This should also mention that EXI has been registered as an HTTP content coding, and can be used. It has the substantial advantage that in most configurations it is smaller while also requiring fewer cycles to decode.
"For very small files (e.g. <1k) the negative impact of processing may outweigh any small transport gains." Note that for very small files, gzip will render them larger anyway.
One suggestion to add here is to prioritise your network requests and
throttle the number of connections in order to ensure that high
priority requests are not blocked or slowed by lower priority
requests, if they are unable to be batched.
Although this is a different point to 3.1.1 they are related and maybe
should be merged, colocated or reference each other
I don't like this recommendation.
What does "reasonable" mean? What about "manageable"?
What is a 10Mb DOM?
How should people measure it?
Why was this value chosen? (Recent high end browser handle much larger DOMs)
It is unclear what the recommendation to "Clip content and separate
content onto separate pages" means.
Are you saying to make top level URL changes to download new pages
(and parse new JS)? If you are I think that is a bad recommendation as
the latency hit is quite bad.
Typically a better solution is to rather than hide non visible DOM
elements, to instead remove these elements from the DOM altogether and
recreate them as needed.
Add a comment.