On 2015-04-02 09:56, Jeffrey Yasskin wrote:
It seems like a CG is appropriate for the Sockets API. It's not clear
that a browser is going to adopt it unless the Trust & Permissions CG
comes up something, but if more native platforms like Cordova and FFOS
want to coordinate on a shared interfa
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22540
Joshua Bell changed:
What|Removed |Added
Resolution|LATER |FIXED
--- Comment #8 from Joshua Bell -
It seems like a CG is appropriate for the Sockets API. It's not clear that
a browser is going to adopt it unless the Trust & Permissions CG comes up
something, but if more native platforms like Cordova and FFOS want to
coordinate on a shared interface, a CG is a good place to iterate on that.
If it
On 4/2/15 8:15 AM, Simon Pieters wrote:
http://www.w3c-test.org/websockets/keeping-connection-open/001.html --
the test is wrong. Passing undefined means the argument is not
present per Web IDL, so this should not throw.
I assume you mean some other test since that test doesn't use undefined.
Boom!
http://pixelscommander.com/en/web-applications-performance/render-html-css-in-webgl-to-get-highest-performance-possibl/
This looks pretty amazing.
On Sat, Feb 14, 2015 at 4:01 PM, Brendan Eich
wrote:
> Hang on a sec before going off to a private or single-vendor thread
> because you thin
On Thu, 26 Mar 2015 18:06:15 +0100, Boris Zbarsky wrote:
On 3/26/15 1:02 PM, Boris Zbarsky wrote:
It looks like the tests that are failed with an "Error" as opposed to a
"Fail" are not being counted in the "<2 passes" list?
And the for
http://www.w3c-test.org/websockets/keeping-connection-
On Thu, 26 Mar 2015 16:37:28 +0100, Olli Pettay wrote:
websockets/interfaces.html the test itself has bugs (uses old
idlharness.js?).
https://github.com/w3c/web-platform-tests/pull/1714
--
Simon Pieters
Opera Software
On Thu, 26 Mar 2015 16:37:28 +0100, Olli Pettay wrote:
Also websockets/interfaces/WebSocket/events/013.html is buggy. Seems to
rely on blink/presto's EventHandler behavior, which is not
what the specs says should happen.
It probably matched the spec at the time the test was written.
Spec n
On Thu, Apr 2, 2015 at 2:40 PM, Anders Rundgren <
anders.rundgren@gmail.com> wrote:
>
> Obviously we need a model where the code is "vetted" for
> DoingTheRightThing(tm).
>
This is essentially about two things: trust and the capability to "vet".
Both of these things cannot be solved conclusive
On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters wrote:
http://www.w3c-test.org/websockets/interfaces/WebSocket/readyState/003.html
looks wrong to me: the value it should get is in fact undefined, since
the property got deleted from the prototype.
(Will have a look.)
http://heycam.githu
On 2015-04-02 11:46, Nilsson, Claes1 wrote:
Thanks for all replies to my mail below.
To address the “security/webapp permission to use the API”- issue I see the
following alternatives:
1.Keep as is: This means that the way permission is given to a webapp to use
the API is not defined by the
On Thu, 02 Apr 2015 14:15:10 +0200, Simon Pieters wrote:
http://www.w3c-test.org/websockets/keeping-connection-open/001.html --
the test is wrong. Passing undefined means the argument is not present
per Web IDL, so this should not throw.
I assume you mean some other test since that test d
On Thu, 26 Mar 2015 18:24:22 +0100, Boris Zbarsky wrote:
On 3/26/15 10:51 AM, Arthur Barstow wrote:
If anyone is willing to help with the failure analysis, that would be
very much appreciated.
Taking a brief look at some of the failures in Firefox, in addition to
the ones Olli already post
Thanks for all replies to my mail below.
To address the "security/webapp permission to use the API"- issue I see the
following alternatives:
1. Keep as is: This means that the way permission is given to a webapp to
use the API is not defined by the TCP and UDP Socket API, only methods to
14 matches
Mail list logo
