So in the grand rewrite of fetch I wonder:
1) How does HTML distinguish for which fetch the tasks are queued?
2) How do we deal with tasks for uploading data? Currently fetch only
deals with processing incoming data, not outgoing.
In both these cases, how do we either allow the caller to filter
The problem I'm trying to solve is sending Unicode text to consumers who
need base64-encoded input. Right now the only sane way to do it (and
I quote sane for obvious reasons) is something like the example at
https://developer.mozilla.org/en-US/docs/DOM/window.btoa#Unicode_Strings
It seems
On Sunday 2013-02-17 11:35 -0600, Glenn Maynard wrote:
On Mon, Jan 21, 2013 at 8:39 AM, L. David Baron dba...@dbaron.org wrote:
But I think it's a large amount of extra implementation complexity
to honor @-rules whose purpose is to build global dictionaries (in
particular, @keyframes and
On Mon, Mar 4, 2013 at 9:09 AM, Boris Zbarsky bzbar...@mit.edu wrote:
The problem I'm trying to solve is sending Unicode text to consumers who
need base64-encoded input. Right now the only sane way to do it (and I
quote sane for obvious reasons) is something like the example at
On Mon, 4 Mar 2013, Anne van Kesteren wrote:
So in the grand rewrite of fetch I wonder:
1) How does HTML distinguish for which fetch the tasks are queued?
How do you mean?
2) How do we deal with tasks for uploading data? Currently fetch only
deals with processing incoming data, not
