Hello Marcos
Thank You, I am okay with the changes.
rgds
viji
On Tuesday 02 November 2010 08:20 PM, Marcos Caceres wrote:
On Tue, Nov 2, 2010 at 9:36 AM, viji wrote:
Hello Marcos
The changes for "Email attribute" and "Rule for Getting Text Content with
Normalized White Space" seem fine.
On 11/2/10 11:35 PM, Jonas Sicking wrote:
So your concern is that jQuery will update to use the new API before
browsers implement it. And then once browsers do implement it and
start honoring the .responseType by making various existing properties
throw, things will fail?
No, my concern is that
On Mon, Nov 1, 2010 at 9:39 PM, Boris Zbarsky wrote:
>>> As long as only one entity is doing the expecting, right? Right now
>>> jquery
>>> expects to get responseText, so if you expect something else you can't
>>> use
>>> jquery's XHR wrappers, say
>>
>> I'm not terribly worried about libra
On 11/2/10 4:04 PM, David Flanagan wrote:
Boris (Mozilla) worries that creating a new mode in which responseText
is unavailable will break jQuery applications.
And various others where the consumer of the data and the XHR creator
are not the same entity. jQuery is just an obvious example that
I just had a short talk with Darin Fisher and he suggested that instead of
.responseType taking a string value, that it could be an enum value of
XMLHttpRequest, something like:
const unsigned short RESPONSETYPE_DEFAULT = 0;
const unsigned short RESPONSETYPE_BINARY = 1;
con
Garrett Smith:
> OK, glad we're on the same page. I think the wording of WebIDL should
> be changed to reflect that because what it has now suggests passing a
> copy. Instead, the method that accepts the object uses it for a copy
> and discards it (this method can be trusted not to leak memory of t
On 11/02/2010 01:30 PM, James Robinson wrote:
On Tue, Nov 2, 2010 at 1:04 PM, David Flanagan mailto:da...@davidflanagan.com>> wrote:
Is this a fair summary of this thread?
Chris (Apple) worries that having to support both responseText and
responseArrayBuffer will be memory inefficie
On Tue, Nov 2, 2010 at 1:04 PM, David Flanagan wrote:
> Is this a fair summary of this thread?
>
> Chris (Apple) worries that having to support both responseText and
> responseArrayBuffer will be memory inefficient because implementations will
> end up with both representations in memory.
>
>
Ther
Is this a fair summary of this thread?
Chris (Apple) worries that having to support both responseText and
responseArrayBuffer will be memory inefficient because implementations
will end up with both representations in memory.
James (Google) worries that synchronously reading bytes from the br
We're meeting tomorrow (Wednesday) at 12:30 at room #4 on the third floor to
continue IndexedDB discussions. The plan is to go grab lunch somewhere and
then come back to room #4 and discuss stuff. The main topics will be error
handling and arrays/compound-keys/etc.
J
On Tue, Nov 2, 2010 at 2:07
On Tue, Nov 2, 2010 at 9:36 AM, viji wrote:
> Hello Marcos
>
> The changes for "Email attribute" and "Rule for Getting Text Content with
> Normalized White Space" seem fine.
Good to hear!
> I have a comment on usage of Global attributes for Icon, Feature, Content
> and Param elements.
>
> Fo
Propose:
can implementors provide an update on their implementation status/plans?
Nikunj
On Nov 2, 2010, at 3:58 AM, Jeremy Orlow wrote:
> Great list!
>
> I propose we start with the various keys issues (I think we can make a lot of
> progress quickly and it's somewhat fresh on our minds), go
Not sure if this is covered by "index keys", but you may consider adding:
- Full-text indexing
To the agenda.
N
On Tue, Nov 2, 2010 at 11:15 AM, Jonas Sicking wrote:
> I suspect internationalization is another thing where we can quickly
> make progress so lets try to get to that one too.
>
I suspect internationalization is another thing where we can quickly
make progress so lets try to get to that one too.
/ Jonas
On Tue, Nov 2, 2010 at 11:58 AM, Jeremy Orlow wrote:
> Great list!
> I propose we start with the various keys issues (I think we can make a lot
> of progress quickly and
Great list!
I propose we start with the various keys issues (I think we can make a lot
of progress quickly and it's somewhat fresh on our minds), go to dynamic
transactions (mainly are we going to support them), and then go from there.
J
On Tue, Nov 2, 2010 at 10:48 AM, Pablo Castro wrote:
> To
To hit the ground running on this, here is a consolidated list of issues coming
both from the thread below and various pending bugs/discussions we've had. I
picked an arbitrary order and grouping, feel free to tweak in any way.
- keys (arrays as keys, compound keys, general keypath restrictions)
Hello Marcos
The changes for "Email attribute" and "Rule for Getting Text Content
with Normalized White Space" seem fine.
I have a comment on usage of Global attributes for Icon, Feature,
Content and Param elements.
For all these elements dir attribute does not make sense. The text yo
On 1 Nov 2010, at 13:19, Bryan Sullivan wrote:
> Hi,
> Can anyone point to an example of how to use HTTP redirect-based protocols
> such as OAuth with widgets? There seem to be issues with the use of these
> protocols due to the difference between widgets and browser-based webapps, in
> part
On 10/31/10, Cameron McCormack wrote:
> Garrett Smith:
[...]
>> The difference here is that the object that was passed in uses normal
>> ES syntax; it's pass by value (value of reference) not referenced by
>> the object. The effect is what you wanted, I think, and that is that
>> 1) the method t
19 matches
Mail list logo
