On Wed, Sep 9, 2009 at 5:55 PM, Marcos Caceres marc...@opera.com wrote:
During testing I discovered that the preference element is under specified
(sorry, y'all!). It is not clear what the user agent is supposed to do when
encountering the following:
preference name=a value=a/
preference
There has already been a discussion on extending XMLHttpRequest.send() to
take a File object. Could we also consider enhancing it further to support
sending multiple files, like a FileList from the drag and drop.
We could make XMLHttpRequest.send() take a FileList object and let the
browser add
On Thu, 10 Sep 2009 03:12:52 +0200, Jian Li jia...@chromium.org wrote:
There has already been a discussion on extending XMLHttpRequest.send() to
take a File object. Could we also consider enhancing it further to
support
sending multiple files, like a FileList from the drag and drop.
We could
On Sep 10, 2009, at 4:29 AM, ext Marcos Caceres wrote:
After some discussion with Artb on IRC [1], we concluded that option 1
above is the preferred behavior (it is consistent with the behavior of
other elements). I will specify that behavior in the PC Test Suite
Edition. If anyone objects,
On Tue, Sep 8, 2009 at 5:47 PM, Marcos Caceresmarc...@opera.com wrote:
Marcin Hanclik wrote:
Hi Marcos,
Thanks for your comments.
It seems we are aligned.
UAs will just have to deal with that internally
I assume there could be an easy solution to the normalization:
The normalization /
On Tue, Sep 8, 2009 at 5:47 PM, Marcos Caceresmarc...@opera.com wrote:
Marcin Hanclik wrote:
Hi Marcos,
Thanks for your comments.
It seems we are aligned.
UAs will just have to deal with that internally
I assume there could be an easy solution to the normalization:
The normalization /
Is the fundamental difference of feature and access the following:
feature - API set expected to be possibly used
access - network resource to be accessed.
if so, doesn't feature imply both the loading and permission to access
a library, whereas access is about accessing a resource.
if this
The draft minutes from the 10 September Widgets voice conference are
available at the following and copied below:
http://www.w3.org/2009/09/10-wam-minutes.html
WG Members - if you have any comments, corrections, etc., please send
them to the public-webapps mail list before 17 September
Below are some comments about Sections 6. (and its sub-sections) of
the 18-Aug-2009 LCWD of the AE spec:
http://www.w3.org/TR/2009/WD-widgets-apis-20090818/
-Regards, Art Barstow
1. I don't understand the statement:
[[
A user agent must implement the Widget interface as a widget
