On Mon, Nov 10, 2014 at 9:57 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 11/10/14, 12:45 PM, Dimitri Glazkov wrote:
FWIW, it is perfectly reasonable for us to admit that we as a platform
aim to always be years behind other platforms. But then we should make
this clear and communicate it to
On Mon, Nov 10, 2014 at 5:33 PM, Brendan Eich bren...@secure.meer.net
wrote:
Right.
Didn't we have a problem with Canvas's string-based getContext already?
http://robert.ocallahan.org/2012/05/canvas-getcontext-mistake.html
Domenic's question still needs addressing separately, but just a
[ Bcc: public-review-announce ]
All,
This is a Request for Comments for the November 13 Last Call Working
Draft of WebAppSec's Mixed Content specification:
http://www.w3.org/TR/2014/WD-mixed-content-20141113/
Please see in particular the spec's Modifications to WebSockets
section
On Mon, Nov 10, 2014 at 3:14 PM, Domenic Denicola d...@domenic.me wrote:
From: Dimitri Glazkov [mailto:dglaz...@google.com]
It's still not clear to me what the advantage is of creating a
framework for designing proprietary APIs.
If we don't do something like this as a platform, we'd be
Dimitri Glazkov wrote:
Domenic's question still needs addressing separately, but just a quick
response here -- the API roc described there is different. Tubes are
just like talking to a worker or any MessagePort. There is no extra
API surface emerging from getContext-like function call.
Any
-Brad's PayPal address (which probably bounces now), +Brad's other address.
Thanks for widening the audience!
On Tue, Nov 11, 2014 at 3:39 AM, Arthur Barstow art.bars...@gmail.com
wrote:
Brad, Mike - other than the Modifications to WebSockets section, if
there are any other specific
