On 03/02/2008 03:02 PM, Ian Hickson wrote:
On Tue, 31 Jul 2007, Philip Taylor wrote:
IE undocumentedly recognises some which nobody else does:
aafsU+206D ACTIVATE ARABIC FORM SHAPING
ass U+206B ACTIVATE SYMMETRIC SWAPPING
iafsU+206C INHIBIT ARABIC FORM SHAPING
iss U+206A
On 7/22/14, 7:46 AM, milakam wrote:
Guess it could be similar to the beforescriptexecute
So you don't care if the script data is loaded (by the preload scanner),
only whether it's executed?
-Boris
On Mon, 21 Jul 2014, Ben Maurer wrote:
(1) Allowing the user to specify parameters to Fetch. For example, a user
could say:
script src=/my.js params={'headers':{'myheader':'value'}}
id=myscript /
This would allow the user to make any type of request customization that
they could for a
On Tue, Jul 22, 2014 at 10:26 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 21 Jul 2014, Ben Maurer wrote:
(1) Allowing the user to specify parameters to Fetch. For example, a user
could say:
script src=/my.js params={'headers':{'myheader':'value'}}
id=myscript /
This would allow
On 7/22/14, 2:01 PM, Ben Maurer wrote:
One advantage of doing this is that if there is some use case a site has
that isn't met by the dependency model they can still manually separate the
fetch of an object from its insertion into the DOM.
One issue worth considering here: there are various
Nothing prevents a website from downloading content via fetch/XHR and
simply inserting that text into the DOM. For example, Gmail seems to fetch
many of its resources this way today. This API seems strictly better than a
site that fetches text and just inserts it into the DOM.
Also, it seems like
On 7/22/14, 2:57 PM, Ben Maurer wrote:
Nothing prevents a website from downloading content via fetch/XHR and
simply inserting that text into the DOM.
Yes, I know that. But we're trying to develop a better API so sites
won't need/want to do that anymore, right? All I'm saying is that we
On Tue, Jul 22, 2014 at 11:01 AM, Ben Maurer ben.mau...@gmail.com wrote:
On Tue, Jul 22, 2014 at 10:26 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 21 Jul 2014, Ben Maurer wrote:
(1) Allowing the user to specify parameters to Fetch. For example, a
user
could say:
script src=/my.js
On Tue, Jul 22, 2014 at 12:03 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 7/22/14, 2:57 PM, Ben Maurer wrote:
Nothing prevents a website from downloading content via fetch/XHR and
simply inserting that text into the DOM.
Yes, I know that. But we're trying to develop a better API so sites
I'm pretty new to this spec overall, so please tell me if I'm totally off
track here -- the fetch spec states that it's goal is To unify fetching
across the web platform by providing consistent handling of things such
as CSP or priorities. It seems like the ultimate goal here is that the
http://fetch.spec.whatwg.org/#fetching says:
Otherwise, if response's body is non-null, run these substeps:
Every 50ms or whenever response's body's is pushed to, whichever is least
frequent and as long as response has no termination reason and end-of-file
has not been pushed, queue a task to
To follow this up with a concrete suggestion:
var myfetch = window.fetch('my.css', {'fetch-as': 'stylesheet'});
myfetch.then(function(resp) {
document.body.appendChild(resp.body.asStyleSheet());
});
You can only call asStyleShet if fetch-as=stylesheet. Passing this
parameter would cause the
I think it's from the old XHR spec. Originally this algorithm was
introduced in the XHR spec to fire progress ProgressEvents. In
refactoring of the XHR spec into current XHR spec and Fetch spec, it's
placed in the Fetch spec part, and now is referred from the Fetch API spec
in the Fetch spec
On Tue, 22 Jul 2014, Ben Maurer wrote:
To follow this up with a concrete suggestion:
var myfetch = window.fetch('my.css', {'fetch-as': 'stylesheet'});
myfetch.then(function(resp) {
document.body.appendChild(resp.body.asStyleSheet());
});
...
Why not:
var mystyle = E('link', { rel:
Thanks for the explanation. Does that mean that the current wording is
suboptimal and should be fixed? I don't think it's advisable to say that
response body processing in general should have these delays. But maybe I
just don't fully understand what processing means.
On Jul 22, 2014 4:42 PM,
I like how fetch is a small primitive right now. We should not overload it with
more functionality, but instead create new APIs on top of it. It's important to
be able to polyfill those APIs on top of fetch, instead of adding more stuff to
the base substrate of fetch itself.
On 7/22/14, 7:07 PM, Ben Maurer wrote:
var myfetch = window.fetch('my.css', {'fetch-as': 'stylesheet'});
myfetch.then(function(resp) {
document.body.appendChild(resp.body.asStyleSheet());
});
Boris, Will -- would this setup address the concerns you have about the
problems websites that use
+annevk
process response body in the XHR spec is only handling errors and firing
a readystatechange event and ProgressEvents. response in the XHR spec [1]
is set to the argument response of process response hook. I think this
set means making response [1] point to the response in the Fetch spec
Hi,
As the spec currently stands, use of input type=number is unsuitable
for currency and other input that require a minimum number of decimal
points displayed. When displaying decimal currency values, the typical
convention is that a precision of two decimal points is used,
regardless of
19 matches
Mail list logo
