/2009AprJun/1000.html
I haven't really given it another thought yet, as I'm hoping a few other people
will take a crack at it first.
Cheers,
--
Anne van Kesteren
http://annevankesteren.nl/
-byte-length-based uses of it. Is that really a good idea? (I suppose that
could be a different interface that extends ProgressEvent, but still.)
--
Anne van Kesteren
http://annevankesteren.nl/
.
--
Anne van Kesteren
http://annevankesteren.nl/
to think of it, maybe
we should ask them to email some feedback on file API design to this list?
--
Anne van Kesteren
http://annevankesteren.nl/
is that you are duplicating some interfaces we have
under development:
http://www.w3.org/TR/2009/WD-cssom-view-20090804/#the-media-interface
--
Anne van Kesteren
http://annevankesteren.nl/
I believe it is the idea that Web Sockets will support sending and
receiving structured clones. It might make sense to define that format
sooner rather than later so implementations of Web Storage that support
structured clones can use it.
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 09 Sep 2009 19:41:38 +0200, Jonas Sicking jo...@sicking.cc wrote:
On Wed, Sep 9, 2009 at 7:14 AM, Anne van Kesteren ann...@opera.com
wrote:
I believe it is the idea that Web Sockets will support sending and
receiving structured clones. It might make sense to define that format
not matter much.
Anyway, this was supposed to be a very simple request. If it's not clear
then lets drop it. Changing some serialization code later on shouldn't be
much of a problem.
--
Anne van Kesteren
http://annevankesteren.nl/
seems a lot less error-prone for authors. I think we should go
with that.
--
Anne van Kesteren
http://annevankesteren.nl/
by a DOMString is the wrong
way to go for Web Platform APIs the original request was about sending a
list of File objects. sendAsBinary does not do that per the documentation.
--
Anne van Kesteren
http://annevankesteren.nl/
) not dispatching an event until the
next character after carriage return has been received which could lead
to delays in event dispatch. Both these options are far from ideal.
The first option should not be too hard to implement right? Just a simple
state variable in the tokenizer.
--
Anne van Kesteren
On Tue, 22 Sep 2009 11:05:26 +0200, Per-Erik Brodin
per-erik.bro...@ericsson.com wrote:
Anne van Kesteren wrote:
On Mon, 21 Sep 2009 17:39:14 +0200, Per-Erik Brodin wrote:
So what you are saying is that \r\n will always be a Windows line
ending and never a Mac line ending followed by a Unix
actually changed my mind on this one and think that using CORS
for this is an abuse of CORS.)
Thanks to you both!
--
Anne van Kesteren
http://annevankesteren.nl/
relatively simple and works with the preflight result
cache.
Kind regards,
--
Anne van Kesteren
http://annevankesteren.nl/
such as
http://tools.ietf.org/html/draft-decroy-http-progress-00 ever get
deployed...
I don't think exposing HTTP 1xx status codes has been discussed before.
--
Anne van Kesteren
http://annevankesteren.nl/
/XMLHttpRequest-2/#differences
(Quite a while ago, but it seems I did not reply to this email.)
--
Anne van Kesteren
http://annevankesteren.nl/
.
(Personally I get quite lost in the sea of terminology used on that page
:-))
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 23 Sep 2009 17:56:05 +0200, Adam Barth w...@adambarth.com wrote:
On Wed, Sep 23, 2009 at 5:34 AM, Anne van Kesteren ann...@opera.com
wrote:
For simple cross-origin requests Origin would be a space-separated list
of origins indicating the redirect chain.
When we used this syntax
, 24 Sep 2009 13:17:09 +0200, Anne van Kesteren ann...@opera.com
wrote:
That would also allow multiple headers to be used I think. Since
Access-Control-Allow-Origin needs to have an identical value to the
Origin header I do not think that would work well. Well, it would
probably work
the
specifications at this point.
--
Anne van Kesteren
http://annevankesteren.nl/
-expressed catchalls map to future EcmaScript should co-evolve
with the changes to EcmaScript needed to support this mapping.
--
Anne van Kesteren
http://annevankesteren.nl/
be nice to have a single
pointer for the draft.)
--
Anne van Kesteren
http://annevankesteren.nl/
of WebIDL.
Of course, other things are never equal. Why do these other projects
need a new version of WebIDL?
There is no old version.
--
Anne van Kesteren
http://annevankesteren.nl/
sufficient examples that show
that the extra protection does not add anything which you would then
forward to the security people from Mozilla and give us the outcome. Based
on that and other evaluations we could then decide whether to keep the
requirement in the specification.
--
Anne van
While adding the Last-Event-ID header to CORS I noticed that the
Server-Sent Events specification does not list it under IANA
considerations. It should be added there.
--
Anne van Kesteren
http://annevankesteren.nl/
specifications mentioned throughout the draft.
* Removed the @font-face construct use case per a comment.
I suggest we try to resolve the remaining open issues in the issue tracker
during the F2F. It would also be good if someone could volunteer for a
test suite.
--
Anne van Kesteren
http
different way). Thanks!
--
Anne van Kesteren
http://annevankesteren.nl/
it there. Otherwise I suggest we consider this
resolved considering that implementations are shipping.
I personally think keeping the API the way it is now is nicer and the
security issue seems highly theoretical.
--
Anne van Kesteren
http://annevankesteren.nl/
.
--
Anne van Kesteren
http://annevankesteren.nl/
van Kesteren
http://annevankesteren.nl/
On Tue, 17 Jun 2008 05:24:48 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
Anne van Kesteren wrote:
It would change the conformance criteria. I'm not sure that's a good
idea. Especially since the use case put forward is mostly theoretical.
Overall, I'm still not convinced this is a good idea
?
It is enumerated in the terminology section basically:
http://dev.w3.org/2006/webapi/XMLHttpRequest/#terminology
Kind regards,
--
Anne van Kesteren
http://annevankesteren.nl/
. By the time they do
not seem theoretical, it is too late to do better than patch around
problems that should not have been introduced. We've been over this
before.
Agreed.
--
Anne van Kesteren
http://annevankesteren.nl/
help me if they were made more concrete.
confused deputy does not help me much because I don't see the problem
you are seeing.
--
Anne van Kesteren
http://annevankesteren.nl/
that is attached to the uuid.
--
Anne van Kesteren
http://annevankesteren.nl/
On Thu, 08 Oct 2009 19:03:03 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/8/09 11:21 AM, Anne van Kesteren wrote:
I realize this discussion was well over a year ago. I imagine Gecko has
meanwhile dealt with the compatibility issues so we can probably keep it
in the specification if you
apologies for coming
over as annoyed, I'm not. Just somewhat confused.)
--
Anne van Kesteren
http://annevankesteren.nl/
On Mon, 12 Oct 2009 17:51:45 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/12/09 5:06 AM, Anne van Kesteren wrote:
FWIW, this is what I've done now. It gives authors a reasonable level of
control over the Content-Type header, it does make sure an incorrect
charset parameter is fixed
On Tue, 13 Oct 2009 19:48:09 +0200, Peter Michaux petermich...@gmail.com
wrote:
It seems as though the new version is not posted. Is there somewhere I
can see the changed text?
Did you follow the link to the latest editor's draft?
http://dev.w3.org/2006/webapi/XMLHttpRequest/
--
Anne van
of the implementations, or the CSSOM spec along with some
of the implementations, or both.
FWIW, the plan is to change CSSOM to serialize to lowercase digits
instead. Much like canvas.
--
Anne van Kesteren
http://annevankesteren.nl/
-20081222-errata#S1
Didn't we explicit decide against this because you could easily feature
test it?
--
Anne van Kesteren
http://annevankesteren.nl/
it to be honest. Because for appcache
total and loaded would always be 0 and for XMLHttpRequest totalItems and
loadedITems would always be 0.
Are there any other cases worth considering?
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 20 Oct 2009 02:10:43 +0200, Charles McCathieNevile
cha...@opera.com wrote:
On Mon, 19 Oct 2009 20:13:23 +0200, Anne van Kesteren ann...@opera.com
wrote:
If only a subset of the attributes ends up being used, i.e. appcache is
not going to dispatch progress events more often than one
encoding.
Thoughts?
I think for a lot of authors the easiest would be easiest if it was in the
form of multipart/form-data as then they do not have to do anything
special to get the data on the server.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 20 Oct 2009 11:34:16 +0200, Charles McCathieNevile
cha...@opera.com wrote:
On Tue, 20 Oct 2009 10:26:08 +0200, Anne van Kesteren ann...@opera.com
wrote:
The problem with this use case is that it does not map to any API. If
you would implement this the fetching of emails might happen
On Tue, 20 Oct 2009 10:56:47 +0200, Darin Fisher da...@chromium.org
wrote:
On Tue, Oct 20, 2009 at 1:37 AM, Anne van Kesteren ann...@opera.com
wrote:
I think for a lot of authors the easiest would be easiest if it was in
the form of multipart/form-data as then they do not have to do anything
On Tue, 20 Oct 2009 18:27:36 +0200, Darin Fisher da...@chromium.org
wrote:
On Tue, Oct 20, 2009 at 4:31 AM, Anne van Kesteren ann...@opera.com
wrote:
If eventually we get native support for octet-arrays and all we can at
that point add the ability to XMLHttpRequest so you can send anything
On Tue, 20 Oct 2009 20:00:27 +0200, Charles McCathieNevile
cha...@opera.com wrote:
On Tue, 20 Oct 2009 13:14:00 +0200, Anne van Kesteren ann...@opera.com
wrote:
Actually that request would not change anything. As far as
XMLHttpRequest goes it would still transfer only a single entity
implementation will be a necessary part of your CR exit criteria --
could you please confirm that?
I'm not sure how that would work. Demonstrating you can implement this in
Python or PHP?
--
Anne van Kesteren
http://annevankesteren.nl/
, and then delivering data through either a new event, or
through existing progress events.
I'm not really in favor of that. XMLHttpRequest is complicated enough as
it is (and not really interoperable either yet).
--
Anne van Kesteren
http://annevankesteren.nl/
downloads?
For the use cases I can think of it seems that video, audio,
Server-Sent Events, and Web Sockets address them quite nicely.
--
Anne van Kesteren
http://annevankesteren.nl/
and the
same as far as servers are concerned.
--
Anne van Kesteren
http://annevankesteren.nl/
I don't see a reason why we should call the member urn. URL is much more
consistent with other parts of the Web platform and works just as well. I
thought we agreed on this previously so I'm just mentioning it here since
it seems to have changed again.
--
Anne van Kesteren
http
On Mon, 02 Nov 2009 23:46:30 -0800, Adam Barth w...@adambarth.com wrote:
It is somewhat frustrating to be unable to participate in this forum.
Any particular reason you cannot be here? Would be nice if you could come.
Cheers,
--
Anne van Kesteren
http://annevankesteren.nl/
by
the current model?
--
Anne van Kesteren
http://annevankesteren.nl/
use different evaluation strategies for the same
query.
From what I understood so far this would also be the case with the Web
B-Tree Database proposal (maybe even more so given that all SQL
implementations currently have the same underlying engine). Am I missing
something?
--
Anne van
the week of November 9. Does that work?
Sure. We might start on things sooner, but it doesn't mean it can't be
revised.
Do you have a demo implementation already? :-)
--
Anne van Kesteren
http://annevankesteren.nl/
I resolved ISSUE-103 by removing exceptions for the getters as discussed
during the F2F meeting. I don't believe there is anything else outstanding
so we can try another Last Call I think. Do we need a CfC through email as
well maybe before I request to publish that?
--
Anne van Kesteren
http
The name of the file as a UTF8-encoded string. A DOMString is not
UTF-8-encoded. I think this should just say Returns the filename. It is
not more complicated than that as far as I can tell.
--
Anne van Kesteren
http://annevankesteren.nl/
It might make sense to rename INITIAL to EMPTY for consistency with
HTMLMediaElement. Instead of LOADING READING might be better though I care
less about that one.
--
Anne van Kesteren
http://annevankesteren.nl/
various issues with how the read methods are defined in
terms of event handling and task queues, but those can be resolved after
the general API is agreed upon I suppose.)
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 10 Nov 2009 17:53:14 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
On 11/10/09 8:33 PM, Anne van Kesteren wrote:
This should be a bit more exact as to how the mediaType is returned. I
would prefer ASCII-lowercase. Returning application/octet-stream
rather than null also seems better
not copy. I rather
copy how the generic abort error network steps behave.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 10 Nov 2009 18:41:32 +0100, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Nov 10, 2009 at 9:29 AM, Anne van Kesteren ann...@opera.com
wrote:
abort() has some legacy attached to it that I rather not copy.
Such as?
Actually, apart from switching the state to 0 in the end
On Wed, 11 Nov 2009 02:39:46 +0100, Maciej Stachowiak m...@apple.com
wrote:
On Nov 10, 2009, at 5:29 PM, Anne van Kesteren wrote:
The name of the file as a UTF8-encoded string. A DOMString is not
UTF-8-encoded. I think this should just say Returns the filename.
It is not more complicated than
On Thu, 12 Nov 2009 07:45:30 +0100, Julian Reschke julian.resc...@gmx.de
wrote:
Anne van Kesteren wrote:
I don't see a reason why we should call the member urn. URL is much
more consistent with other parts of the Web platform and works just as
well. I thought we agreed on this previously so
and external groups?
HTTP WG, Device APIs WG, HTML WG (due to dependencies),
Internationalization Core WG (they commented before) and maybe the TAG?
Every group is of course welcome to provide review. In fact, encouraged.
Cheers,
--
Anne van Kesteren
http://annevankesteren.nl/
On Wed, 11 Nov 2009 00:03:07 +0100, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Nov 10, 2009 at 10:17 AM, Anne van Kesteren ann...@opera.com
wrote:
Anyway, do you have opinions on the synchronous case? Do you agree we
should use TIMEOUT_ERR there? What do the people from Microsoft think
On Fri, 13 Nov 2009 11:31:03 +0100, Arun Ranganathan a...@mozilla.com
wrote:
Anne van Kesteren wrote:
It might make sense to rename INITIAL to EMPTY for consistency with
HTMLMediaElement. Instead of LOADING READING might be better though I
care less about that one.
Done, but I'll point
On Fri, 13 Nov 2009 11:36:33 +0100, Arun Ranganathan a...@mozilla.com
wrote:
Anne van Kesteren wrote:
This should be a bit more exact as to how the mediaType is returned. I
would prefer ASCII-lowercase.
Done.
The current text says the string is ASCII-encoded. That's not true. It's
, and arguably EMPTY is easier to
spell than INITIAL
Yup.
--
Anne van Kesteren
http://annevankesteren.nl/
to be silent on the issue.
That's exactly what should happen, yes. The specification is status code
agnostic apart from redirects. Anything I can do that makes that more
clear?
--
Anne van Kesteren
http://annevankesteren.nl/
at the W3C, then I'm fine with publishing it as a Note (and
possibly continuing work as a WHATWG or webkit.org spec). Until then, I
would prefer to see work continue here.
I agree. I don't get the sudden rush to end this as WG item.
--
Anne van Kesteren
http://annevankesteren.nl/
sending events (which are
arguably somewhat like write) we still use loadstart/... and simply
dispatch them on a distinct object. I've no idea what the file writer API
will look like, but I can imagine we might be able to do the same there.
--
Anne van Kesteren
http://annevankesteren.nl/
you can find it
somewhat easily.
--
Anne van Kesteren
http://annevankesteren.nl/
. It also seems safer in case something comes up
down the road.
--
Anne van Kesteren
http://annevankesteren.nl/
are concerned, as mentioned before.)
--
Anne van Kesteren
http://annevankesteren.nl/
van Kesteren
http://annevankesteren.nl/
that, querySelector(#foo) and getElementById(foo) should work
fine in xml:id implementations and both are much less cumbersome to type.
--
Anne van Kesteren
http://annevankesteren.nl/
to address the same use case scenarios, imo.
--
Anne van Kesteren
http://annevankesteren.nl/
there.)
--
Anne van Kesteren
http://annevankesteren.nl/
what
would be an issue if I make the above changes.
--
Anne van Kesteren
http://annevankesteren.nl/
be used
elsewhere too.
[1] http://www.w3.org/TR/2009/WD-XMLHttpRequest-20091119
[2] http://www.w3.org/TR/2006/WD-XMLHttpRequest-20060405/
[3] http://www.w3.org/TR/2009/WD-XMLHttpRequest-20091119/#dependencies
(I corrected the numbering here.)
--
Anne van Kesteren
http://annevankesteren.nl/
a single term, defined by HTML5.
--
Anne van Kesteren
http://annevankesteren.nl/
part of it:
When the XMLHttpRequest object is used in other contexts their values
will have to be defined as appropriate for that context.
Fixed, thanks!
--
Anne van Kesteren
http://annevankesteren.nl/
2 which requires strict per-header opt-in. Have you talked with
implementors about this?
--
Anne van Kesteren
http://annevankesteren.nl/
are concerned that a per-origin model would not be implemented
correctly. In addition it would be somewhat of a pain in case of different
services maintained by different parties hosted on a single origin which
we expect to be reasonably common.
--
Anne van Kesteren
http://annevankesteren.nl/
mistakes.
I tried to clarify the use cases for CORS here (if more detail is needed
please let me know):
http://dev.w3.org/2006/waf/access-control/#use-cases
It would be nice to have sufficient detail on how each of these would work
with UM so we can evaluate things better.
--
Anne van
be
found here:
http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest-2/xhr-source
--
Anne van Kesteren
http://annevankesteren.nl/
, params).read()
if __name__ == '__main__':
generate_specs()
--
Anne van Kesteren
http://annevankesteren.nl/
on the manner.
--
Anne van Kesteren
http://annevankesteren.nl/
to this behavior as well other browsers are
probably willing to follow. Unless there are strong objections I will
define this behavior in the specification. I.e. byte-inflation for both
setting and getting headers.
--
Anne van Kesteren
http://annevankesteren.nl/
).
At the very least, throwing if the upper byte is non-zero seems like
the right thing to do to prevent silent data loss.
That works for me.
--
Anne van Kesteren
http://annevankesteren.nl/
On Tue, 05 Jan 2010 08:39:26 +0100, Anne van Kesteren ann...@opera.com
wrote:
On Tue, 05 Jan 2010 08:29:53 +0100, Jonas Sicking jo...@sicking.cc
wrote:
At the very least, throwing if the upper byte is non-zero seems like
the right thing to do to prevent silent data loss.
That works for me
of a FPWD.
I look forward to any additional feedback.
It's still not clear to me how the use cases in
http://dev.w3.org/2006/waf/access-control/#use-cases
are done using UMP. My apologies if I missed a reply to my email asking
for that.
--
Anne van Kesteren
http://annevankesteren.nl/
On Sun, 31 Jan 2010 00:45:17 +0100, David Bruant dbru...@ucsd.edu wrote:
Le 30/01/2010 04:41, Anne van Kesteren a écrit :
The idea is actually that a redirect does not involve a state
transition. I have suggested on this mailing list a way to control
whether redirects are followed but due
. I'm
not sure why developer tools would report an error for invoking the
abort() method though. That sounds like a bug.
[1] http://www.w3.org/TR/XMLHttpRequest/#the-abort-method
--
Anne van Kesteren
http://annevankesteren.nl/
On Fri, 29 Jan 2010 14:29:23 +0100, Pedro Santos pedros...@gmail.com
wrote:
Hi, how interest is for you develop new APIs in order to enable a reuse
of the XMLHttpRequest objects, without the need to call abort method?
No need to ask questions twice :-)
--
Anne van Kesteren
http
/
http://dev.w3.org/2006/webapi/XMLHttpRequest-2/
Or review the diff of xhr-source:
http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest-2/xhr-source.diff?r1=1.6r2=1.7f=h
Kind regards,
--
Anne van Kesteren
http://annevankesteren.nl/
the
two, would that be useful?
--
Anne van Kesteren
http://annevankesteren.nl/
201 - 300 of 1634 matches
Mail list logo
