I've read the 2006-08-21 draft of Web Applications 1.0 carefully and I'm
horrified that section 5.9 on persistent storage is being considered as
a web standard - at least in its current form. My objections can be
summarised as:
* Authors failure to handle the implications of global storage.
*
http://www.w3.org/TR/web-forms-2/#the-autocomplete
| The autocomplete attribute applies to the text, password date-related,
| time-related, numeric, email, and url controls.
There needs to be a comma after password.
--
dolphinling
http://dolphinling.net/
Lachlan Hunt wrote:
dolphinling wrote:
http://www.w3.org/TR/web-forms-2/#the-autocomplete
| The autocomplete attribute applies to the text, password date-related,
| time-related, numeric, email, and url controls.
There needs to be a comma after password.
And no comma after email.
No!
On Sun, 27 Aug 2006 19:11:17 +0700, Shannon Baker [EMAIL PROTECTED] wrote:
But why bother? This whole problem is easily solved by allowing data to
be stored with an access control list (ACL). For example the site
developer should be able to specify that a data object be available to
On 8/27/06, Shannon Baker [EMAIL PROTECTED] wrote:
== 1: Authors failure to handle the implications of global storage. ==
First lets talk about the global store (|globalStorage['']) which is
accessible from ALL domains.
This is mentioned in the Security and privacy section; the third
bullet
dolphinling wrote:
Lachlan Hunt wrote:
dolphinling wrote:
http://www.w3.org/TR/web-forms-2/#the-autocomplete
| The autocomplete attribute applies to the text, password date-related,
| time-related, numeric, email, and url controls.
There needs to be a comma after password.
And no comma
