On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren ann...@annevk.nl 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
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/
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,
On Mon, Apr 27, 2015 at 3:58 PM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Apr 27, 2015 at 2:20 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren ann...@annevk.nl wrote:
Currently Chrome supports data URLs inside EventSource whereas in
On Mon, Apr 27, 2015 at 7:37 PM, duanyao duan...@ustc.edu 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
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
在 2015年04月27日 22:58, Jonas Sicking 写道:
On Mon, Apr 27, 2015 at 2:20 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren ann...@annevk.nl wrote:
Currently Chrome supports data URLs inside EventSource whereas in
Firefox EventSource is restricted to
在 2015年04月28日 02:42, Jonas Sicking 写道:
On Mon, Apr 27, 2015 at 7:37 PM, duanyao duan...@ustc.edu 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
On Mon, Apr 27, 2015 at 2:20 PM, Tab Atkins Jr. jackalm...@gmail.com wrote:
On Mon, Apr 27, 2015 at 7:00 AM, Anne van Kesteren ann...@annevk.nl wrote:
Currently Chrome supports data URLs inside EventSource whereas in
Firefox EventSource is restricted to http/https URLs:
