On 3/18/15, acmesquares . wrote:
> Admittedly a wrapper function is trivial, mostly for API consistency, and
> does simply move the callback elsewhere.
>
There is a lot of room for improvement for toBlob.
> However that's not unprecedented as Navigator.mediaDevices.getUserMedia()
> was just a pr
在 2015年04月28日 02:42, Jonas Sicking 写道:
On Mon, Apr 27, 2015 at 7:37 PM, duanyao wrote:
In iframe, srcdoc attribute seems as secure (insecure) as data: URL in src,
so should it be removed from the spec?
The difference there, and in the other examples that you mention, is
that you know that you
On Mon, Apr 27, 2015 at 7:37 PM, duanyao wrote:
> In iframe, srcdoc attribute seems as secure (insecure) as data: URL in src,
> so should it be removed from the spec?
The difference there, and in the other examples that you mention, is
that you know that you are loading content in your own domain
在 2015年04月27日 22:58, Jonas Sicking 写道:
On Mon, Apr 27, 2015 at 2:20 PM, Tab Atkins Jr. wrote:
On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren wrote:
Currently Chrome supports data URLs inside EventSource whereas in
Firefox EventSource is restricted to http/https URLs:
https://bugzilla.
Jumping in at the end here.
As I've said before, I like the general idea of giving pages more
control over scroll restoration, but I don't think we should tie this
to pushState()/replaceState()/onscroll.
My proposal is instead that we add an API like
history.restoreScroll = boolean;
This proper
On Mon, Apr 27, 2015 at 3:58 PM, Jonas Sicking wrote:
> On Mon, Apr 27, 2015 at 2:20 PM, Tab Atkins Jr. wrote:
>> On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren wrote:
>>> Currently Chrome supports data URLs inside EventSource whereas in
>>> Firefox EventSource is restricted to http/https UR
On Mon, Apr 27, 2015 at 2:20 PM, Tab Atkins Jr. wrote:
> On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren wrote:
>> Currently Chrome supports data URLs inside EventSource whereas in
>> Firefox EventSource is restricted to http/https URLs:
>>
>> https://bugzilla.mozilla.org/show_bug.cgi?id=115
On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren wrote:
> Currently Chrome supports data URLs inside EventSource whereas in
> Firefox EventSource is restricted to http/https URLs:
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=1156137
>
> What's the convergence we want here?
It's rather fru
On 4/27/15 10:00 AM, Anne van Kesteren wrote:
Currently Chrome supports data URLs inside EventSource whereas in
Firefox EventSource is restricted to http/https URLs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1156137
What's the convergence we want here?
Note that per current spec, EventS
Currently Chrome supports data URLs inside EventSource whereas in
Firefox EventSource is restricted to http/https URLs:
https://bugzilla.mozilla.org/show_bug.cgi?id=1156137
What's the convergence we want here?
--
https://annevankesteren.nl/
10 matches
Mail list logo
