Hi Arve,
Thanks for your feedback - I'm glad our thinking is along similar lines.
Some responses to your comments below.
Thanks,
Mark
-Original Message-
From: Arve Bersvendsen [mailto:ar...@opera.com]
Sent: 20 January 2009 20:53
To: Priestley, Mark, VF-Group; public-webapps
Subject:
On Thu, 22 Jan 2009 14:25:02 +0100, Priestley, Mark, VF-Group
mark.priest...@vodafone.com wrote:
Hi Arve,
Thanks for your feedback - I'm glad our thinking is along similar lines.
Some responses to your comments below.
Some responses below. Note that I have cut parts to which I have no
Hi Boris,
On Fri, Jan 9, 2009 at 10:20 PM, Boris Zbarsky bzbar...@mit.edu wrote:
A few comments:
1) In section 7.3, boolean attributes are defined to use case-insensitive
matching. Why is that? There doesn't seem to be a definition of
case-insensitive here, which worries me, since
Hi Arve,
I looked briefly at the Widgets 1.0 APIs and Events spec, Working Draft 22
January 2009. Here are a couple of comments.
1.2 Terms and definitions
The definition of widget context is maybe a little bit too recursive to be
useful...
2.2 last sentence:
... meaning such an implementation
The minutes from the January 22 Widgets voice conference are
available at the following and copied below:
http://www.w3.org/2009/01/22-wam-minutes.html
WG Members - if you have any comments, corrections, etc., please send
them to the public-webapps mail list before 29 January 2009 (the
Hi Boris,
On Thu, Jan 22, 2009 at 3:14 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Marcos Caceres wrote:
Ok, I've removed it. This may cause implementations to override files
on systems that don't support case insensitive file names. This should
not be a real problem, as most file system
