On Wed, 29 Apr 2009, John J. Barton wrote:
You only have to think hard about this if you use numeric keys and use
the implied accessors. Just use .setItem(2) and .getItem(2), or use
a non-numeric key, and then there's no confusion.
So why is numeric keys part of the API?
There are no
On Thu, Apr 30, 2009 at 9:12 AM, Ian Hickson i...@hixie.ch wrote:
For Storage objects, I would do an instanceof against the Storage
prototype. There can't be other objects that implement that interface.
that's wrong. what you mean is that any object which implements
Storage will behave as
Ian Hickson wrote:
On Thu, 30 Apr 2009, Sean Hogan wrote:
I'm not sure about all those objects, but my (incomplete) testing of
HTML*Collections indicates that when accessed using array notation:
object[index]; where index object.length
they behave as a readonly array. Which has the
This message is in response to Marcos request to review 18n
proposal/discussion for widgets packaging [1]. I haven't seen any
updates or proposed updates to requirements so I'm going only from
what's in the proposal and what little has been submitted to the list.
Robin's email [2] answers some
Art et al.
I am unable to join this afternoon's call. I submitted inputs for the
i18n/L10n Topic as per action from last week.
http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0436.html
Andy
Hi Robin,
- do we need to say anything about multiple instances of the same
widget?
I think so.
Since widget URI is to help in inter-widget communication, I assume it should
be clarified on the URI level as well, how different instances are to be
handled (or not handled).
What about e.g.
Hi Marcin,
On Apr 30, 2009, at 14:37 , Marcin Hanclik wrote:
- do we need to say anything about multiple instances of the same
widget?
I think so.
Since widget URI is to help in inter-widget communication, I assume
it should be clarified on the URI level as well, how different
instances
Hi Robin,
It is ok for me, if the below clarifications go into the text, into the section
2.
Thanks.
Kind regards,
Marcin
Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452 | Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanc...@access-company.com
On Thu, 30 Apr 2009 16:01:45 +0200, Anne van Kesteren ann...@opera.com wrote:
For environments where the global object is represented by the Window
object XMLHttpRequest needs to be associated with a Document object for
determining the origin and base URL. The problem is that the
Title: [widgets] Comments to access element text
Here are a couple of suggestions for the access element (http://dev.w3.org/2006/waf/widgets/#the-access-element):
Attributes
(add two new attributes)
required: Optional.
A boolean attribute that indicates whether or not this resource is
For environments where the global object is represented by the Window object
XMLHttpRequest needs to be associated with a Document object for determining
the origin and base URL. The problem is that the XMLHttpRequest interface
object can be copied around, e.g.
var x =
Hi,
here's my quick stab at a definition:
- multiple instances of a widget are the same widget (one
installation) being run multiple times in parallel, e.g. a weather
widget that you run once for the weather in Paris and once for the
weather in Sydney;
- multiple invocations of a widget
Hi Bryan,
On Apr 30, 2009, at 16:06 , Sullivan, Bryan wrote:
Here are a couple of suggestions for the access element (http://dev.w3.org/2006/waf/widgets/#the-access-element
):
Attributes
(add two new attributes)
required: Optional.
I'm happy to add a required attribute with the same
On Thu, 30 Apr 2009, Anne van Kesteren wrote:
For environments where the global object is represented by the Window
object XMLHttpRequest needs to be associated with a Document object for
determining the origin and base URL. The problem is that the
XMLHttpRequest interface object can be
On Apr 30, 2009, at 9:58 AM, Ian Hickson wrote:
On Thu, 30 Apr 2009, Anne van Kesteren wrote:
For environments where the global object is represented by the Window
object XMLHttpRequest needs to be associated with a Document object
for
determining the origin and base URL. The problem is
Dear,
On Thu, Apr 30, 2009 at 4:45 PM, Robin Berjon ro...@berjon.com wrote:
Hi,
a) the UA has somehow allowed me to pick which instance I run, I get back
what I put for the right instance
b) the UA has become confused, I get both values, or something broken, or
nothing
c) the UA has a
Hi Robin,
I appreciate the consensus on the required attribute.
The duration attribute is an attempt to address the more fine-grained needs vs
policy alignment that is hinted at in the required flag. As widget runtime
environments are deployed with policy controls on what can be accessed (e.g.
17 matches
Mail list logo
