Re: [whatwg] XSS safe templating

2010-03-23 Thread Alex Russell
On Thu, Mar 11, 2010 at 1:50 AM, Maciej Stachowiak wrote: > > On Mar 10, 2010, at 10:15 AM, Mike Samuel wrote: > >> Hmm.  It occurs to me that many libraries -- at least jQuery and >> prototype have their own layers in between their users and the DOM. >> When I cooked up this scheme, I didn't know

Re: [whatwg] Spec formats

2010-03-23 Thread Perry Smith
On Mar 23, 2010, at 5:29 PM, Ian Hickson wrote: Ok. So basically we are looking for a version of the complete.html file with an override style sheet for black&white and no scripts? I haven't done the styles yet but how's this otherwise?: http://www.whatwg.org/specs/web-apps/current-work/

Re: [whatwg] Spec formats

2010-03-23 Thread Ian Hickson
On Tue, 23 Mar 2010, Perry Smith wrote: > > > > How about the alternative style sheets for authors, and the UI to > > support them? > > I'm not 100% sure I know what you are referring to. I see a radio > button for "Hide UA text". Is that for authors? Yeah. > > Also, which specs do you wan

Re: [whatwg] Spec formats

2010-03-23 Thread Perry Smith
On Mar 23, 2010, at 1:11 AM, Ian Hickson wrote: On Mon, 22 Mar 2010, Perry Smith wrote: On Mar 22, 2010, at 7:00 PM, Ian Hickson wrote: If you would like to generate ePub or other formats of the spec, I would be happy to coordinate with you to set up a system that can do this on a regular ba

Re: [whatwg] WebSocket bufferedAmount includes overhead or not.

2010-03-23 Thread Anne van Kesteren
On Tue, 23 Mar 2010 10:38:27 +0100, Olli Pettay wrote: And I certainly prefer the current behavior, where the API is not so tightly bound to the protocol, and where the bufferedAmount is handled more close to what progress events do with XMLHttpRequest. We (Opera) would prefer this too. I.e.

Re: [whatwg] WebSocket bufferedAmount includes overhead or not.

2010-03-23 Thread Olli Pettay
On 3/18/10 2:15 AM, Alexey Proskuryakov wrote: On 05.03.2010, at 15:32, Alexey Proskuryakov wrote: for something no one should care about, as you implied above. From API perspective I do care. Web developers shouldn't need to know about the protocol, yet (s)he should be able to understand wha