- From: Thomas Roessler <tlr@w3.org>
- Date: Wed, 20 May 2009 13:50:50 +0200
- To: Thomas Roessler <tlr@w3.org>
- Cc: WSC WG public <public-wsc-wg@w3.org>
On 9 May 2009, at 11:48, Thomas Roessler wrote: > Looking at Yngve's message here: > > http://www.w3.org/mid/op.us37ivemvqd7e2@killashandra.oslo.opera.com > > ... I wonder what the next step is. I think we have the following > open points: > > 1. We need to add a MAY clause after the first paragraph of 5.4.1: > >> When TLS error conditions occur, user agents MAY choose to abort >> the connection without any further user interaction. The >> guidelines in this section apply when user agents choose to cause a >> user interaction in the case of TLS error conditions. > > > 2. We might want to make it more clear above that a user agent can > very well both follow the detailed guidance in 5.4.1 (e.g., for the > top-level frame), and choose to do the hard abort in some cases -- > e.g., XMLHttpRequest, and that the latter is indeed the recommended > course of action. Per ACTION-574, I propose to add the following text after the MAY clause given above: > Note that user agents may combine both practices: E.g., an > interactive approach may be chosen for the top-level frame of a Web > page, but a non-interactive approach may be chosen for inline > content. It is expected that the XMLHttpRequest specification will > include a non-interactive approach as well. Thoughts?
Received on Wednesday, 20 May 2009 11:51:02 UTC