Hi Ian and the rest of the list,
We are having a bit of discussion regarding the correct behaviour
when mandatory arguments are undefined, see this webkit bug for history:
https://bugs.webkit.org/show_bug.cgi?id=60622
Could we have some clarification for the below cases, please:
var u;
var n =
Can EventSource be enhanced to support cross-domain requests via
Access-Control-Allow-Origin header, just like it is already done for XHR? See
http://en.wikipedia.org/wiki/XMLHttpRequest#Cross-domain_requests.
I filed a request with WebKit bugzilla and they suggested to send it to you:
Dear Friends of HTML5,
i think i have the topic back on the list in my mind. I know already two
workarounds.
1) Whitelisting the index file (having the manifest) - create a splash
screen to walk through. Whitelist the (previous) master file like a normal
network resource there.
For a CMS with
Me again..
Won´t continue writing down every step. But my next look, i´ll be motivated
now, tells me one thing:
Create a _new header_ with the Interfaces, and work on the manifest
structure. This is what the rest of the files in webkit/appcache do with all
the data.
I shouldn´t write the
2011/6/1 Tommy Widenflycht (ᛏᚮᛘᛘᚤ) tom...@google.com:
Hi Ian and the rest of the list,
We are having a bit of discussion regarding the correct behaviour
when mandatory arguments are undefined, see this webkit bug for history:
https://bugs.webkit.org/show_bug.cgi?id=60622
Could we have some
On Wed, Jun 1, 2011 at 11:23 AM, ilya goberman gober...@msn.com wrote:
Can EventSource be enhanced to support cross-domain requests via
Access-Control-Allow-Origin header, just like it is already done for XHR?
See http://en.wikipedia.org/wiki/XMLHttpRequest#Cross-domain_requests.
I filed a
Tommy Widenflycht (ᛏᚮᛘᛘᚤ):
Could we have some clarification for the below cases, please:
var u;
var n = null;
// Should throw since u is undefined or just abort?
navigator.webkitGetUserMedia(audio, u);
I don’t think Ian has made changes to the spec yet regarding interface
types not
Aryeh Gregor:
But there's an open issue that says Need to test how implementations
actually behave when passed too few or too many arguments. So I
wouldn't assume the standard is right. Maybe data would be useful on
how different browsers behave here -- although I suspect that it will
vary
