- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Mon, 22 Jun 2015 10:45:52 -0700
- To: Mike West <mkwst@google.com>
- Cc: "public-webappsec@w3.org" <public-webappsec@w3.org>, Dan Veditz <dveditz@mozilla.com>, Wendy Seltzer <wseltzer@w3.org>, Brad Hill <hillbrad@gmail.com>, Kristijan Burnik <burnik@google.com>, Brian Smith <brian@briansmith.org>, Ryan Sleevi <sleevi@google.com>
On Mon, Jun 22, 2015 at 7:17 AM, Mike West <mkwst@google.com> wrote: > If you have any comments or concerns regarding this CfC, please reply to > public-webappsec@w3.org by the end of June 6th at the latest. Silence will > be interpreted as glowing praise and full-throated agreement, but I'd > encourage you to praise full-throatedly, glowingly, _and_ explicitly on the > list. :) Looks pretty good. Are there bugs on WebSocket to get the specification updated to take Mixed Content into account? The phrase "That is certainly the intent." can be removed. Also, you need to replace "TLS state" with "HTTPS state". We decided to rename that term together a while back to avoid OE confusion. -- https://annevankesteren.nl/
Received on Monday, 22 June 2015 17:46:18 UTC