On Feb 2, 2010, at 9:42 PM, Tyler Close wrote:
> On Tue, Feb 2, 2010 at 5:14 PM, Maciej Stachowiak wrote:
>>
>> On Feb 2, 2010, at 11:15 AM, Tyler Close wrote:
>>
>>> On Sun, Jan 31, 2010 at 11:03 PM, Maciej Stachowiak wrote:
I'm curious what practical differences there are between CORS
On Tue, Feb 2, 2010 at 5:14 PM, Maciej Stachowiak wrote:
>
> On Feb 2, 2010, at 11:15 AM, Tyler Close wrote:
>
> > On Sun, Jan 31, 2010 at 11:03 PM, Maciej Stachowiak wrote:
> >> I'm curious what practical differences there are between CORS with the
> >> credentials flag
> >> set to false and th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/2/2010 8:37 PM, Pablo Castro wrote:
d. 3.2.4.2: in our experiments writing application code, the
fact that this method throws an exception when an item is not found is
quite inconvenient. It would be much natural to just return undefi
On Mon, Feb 1, 2010 at 1:30 AM, Jeremy Orlow wrote:
> > > 1. Keys and sorting
> > > a. 3.1.1: it would seem that having also date/time values as keys
> > > would be important and it's a common sorting criteria (e.g. as part of a
> > > composite primary key or in general as an index key
I definitely am in favor of this, unsurprisingly given that we've
chosen to do this in Firefox.
/ Jonas
On Tue, Feb 2, 2010 at 5:02 PM, Maciej Stachowiak wrote:
> Hey folks,
>
> Any thoughts on this? I think it would be wise to issue an errata against DOM
> 3 Core to allow caching of NodeLists,
On Feb 2, 2010, at 11:15 AM, Tyler Close wrote:
> On Sun, Jan 31, 2010 at 11:03 PM, Maciej Stachowiak wrote:
>> I'm curious what practical differences there are between CORS with the
>> credentials flag
>> set to false and the origin set to "null", and UMP. Are there any?
>
> The credentials f
On Jan 29, 2010, at 6:36 AM, Sebastian Hennebrueder wrote:
> Arthur Barstow schrieb:
>> Sebastian, All,
>> On Jan 18, 2010, at 10:54 AM, ext Sebastian Hennebrueder wrote:
>>> About half a year ago I came up with an idea to add a unique window id
>>> as request header to each browser request. I pu
Hey folks,
Any thoughts on this? I think it would be wise to issue an errata against DOM 3
Core to allow caching of NodeLists, and make sure to fix this in DOM4. IE and
Firefox seem to do it, and it can be a big performance benefit, so I think the
DOM spec should allow it.
The three errata nee
On 2/2/10 11:56 PM, Jonas Sicking wrote:
The problem with this is one of performance.
And the problem is also how to specify it so that
resize events loops aren't possible (or at least not easy to cause).
What if resize event listener causes a new resize ...
-Olli
Btw, discussion about DOM E
The problem with this is one of performance.
For example resizing the window could easily cause every single
element on the page to change size. If every element fired an event,
that could easily mean firing thousands of events.
Yes, in many situations the implementation could optimize and not fi
On 2/2/10 11:09 PM, Gregg Tavares wrote:
I'm not sure if this is the correct place for this but:
Has there been any discussion of adding an element.onresize event?
The issue that has come up is the canvas tag, in 2d or 3d, when the canvas
changes its displayed size, a webapp might want to respo
I'm not sure if this is the correct place for this but:
Has there been any discussion of adding an element.onresize event?
The issue that has come up is the canvas tag, in 2d or 3d, when the canvas
changes its displayed size, a webapp might want to respond by changing
the size of the internal rep
On Tue, Feb 2, 2010 at 10:36 AM, Zhiheng Wang wrote:
> Hi, Olli,
>
> On Fri, Jan 29, 2010 at 6:15 AM, Olli Pettay wrote:
>
>> On 1/27/10 9:39 AM, Zhiheng Wang wrote:
>>
>>> Folks,
>>>
>>> Thanks to the much feedback from various developers, the WebTiming
>>> specs has undergone some
>>> maj
Hi, Marcos-
Marcos Caceres wrote (on 2/2/10 7:29 AM):
I had a discussion with an implementer who was a bit confused about the
concept of "null" in the specification. The problem is that I kinda
wrote the spec as if it was to be implemented in Java or JavaScript.
This has resulted in confusion w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/1/2010 8:17 PM, Pablo Castro wrote:
> [snip]
>> the existence of currentTransaction in the same class).
>
>> "beginTransaction" would capture semantics more accurately. b.
>> ObjectStoreSync.delete: delete is a Javascript keyword, can we
>> us
On Sun, Jan 31, 2010 at 11:03 PM, Maciej Stachowiak wrote:
> I'm curious what practical differences there are between CORS with the
> credentials flag
> set to false and the origin set to "null", and UMP. Are there any?
The credentials flag in CORS is underspecified, so it's hard to answer
this
Jonas,
On Fri, Jan 29, 2010 at 12:50 AM, Jonas Sicking wrote:
> On Thu, Jan 28, 2010 at 10:53 PM, Zhiheng Wang
> wrote:
>
> >> >> Also, what is the use case for the "Ticks" interface?
> >> >
> >> >The Ticks interface is a convenient way to store time measurements
> >> > and
> >> > retrieve
Hi, Olli,
On Fri, Jan 29, 2010 at 6:15 AM, Olli Pettay wrote:
> On 1/27/10 9:39 AM, Zhiheng Wang wrote:
>
>> Folks,
>>
>> Thanks to the much feedback from various developers, the WebTiming
>> specs has undergone some
>> major revision. Timing info has now been extended to page elements and
All,
As actioned in the 21st Jan teleconference, here are the use cases that have
motivated my specific proposal for supporting local network access in the WARP
spec (see
http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0173.html for
details).
1. A developer wishes to write widge
After looking at the spec a bit more closely, I noticed that the
following requirement from how to process a feature element (Step 7):
"If the name attribute of this feature element is absent, then the
user agent must ignore this element."
I've now added that.
We had tests for this behavior in t
On Tue, Feb 2, 2010 at 2:20 PM, Simon Pieters wrote:
> On Tue, 02 Feb 2010 13:29:42 +0100, Marcos Caceres
> wrote:
>
>> Hi,
>> I had a discussion with an implementer who was a bit confused about the
>> concept of "null" in the specification. The problem is that I kinda wrote
>> the spec as if it
(IMPORTANT: New test in the test suite, please see below if you have
already submitted your results)
On Fri, Jan 29, 2010 at 1:45 PM, Arve Bersvendsen wrote:
> This is an excerpt of something I wrote on the #webapps IRC channel:
>
> hm
> I have some exploratory work here (not going into details
On Tue, 02 Feb 2010 13:29:42 +0100, Marcos Caceres
wrote:
Hi,
I had a discussion with an implementer who was a bit confused about the
concept of "null" in the specification. The problem is that I kinda
wrote the spec as if it was to be implemented in Java or JavaScript.
This has resulte
Thomas Roessler wrote:
Is that a P&C specific concern or one that should better be covered in WebIDL?
It's a P&C concern, not related to WebIDL. I think WebIDL kinda assumes
a layer of abstraction over ECMAScript - this is not the case with P&C
which knows nothing about scripting languages,
Is that a P&C specific concern or one that should better be covered in WebIDL?
--
Thomas Roessler, W3C
On 2 Feb 2010, at 13:29, Marcos Caceres wrote:
> Hi,
> I had a discussion with an implementer who was a bit confused about the
> concept of "null" in the specification. The problem is t
Hi,
I had a discussion with an implementer who was a bit confused about the
concept of "null" in the specification. The problem is that I kinda
wrote the spec as if it was to be implemented in Java or JavaScript.
This has resulted in confusion wrt how "null" is to be interpreted in
languages t
26 matches
Mail list logo
