Re: [whatwg] Canvas line styles comments

On Sat, 2 Feb 2008, Philip Taylor wrote: > > "The lineCap attribute defines the type of endings that UAs shall place > on the end of lines." - it seems weird to use "shall", since this is the > only place in the spec (except the list of RFC2119 keywords) that uses > it. The other line* properti

Re: [whatwg] Canvas comments

On Fri, 1 Feb 2008, Oliver Hunt wrote: > > I believe Hixie is already looking at speccing the ImageData object to > require a fast native backing buffer (i could be wrong), but i'll add my > two cents here. Indeed, that has now been done. > That said i would still very much like to have the ab

Re: [whatwg] SQL storage and onunload

On Feb 9, 2008, at 12:58 PM, Anne van Kesteren wrote: As far as the unload handler question, what are the semantics for XHR? I think the user leaving the page is the same as aborting the download. I've seen servers (e.g. Google) use XHR in onunload to track usage statistics. Sounds

Re: [whatwg] postMessage: event.source allows navigation of sender

I'm a bit late to this party due to turning off list email because I didn't think I could handle it in addition to all the other email I receive. I just reenabled it to not miss anything; we'll see how this actually goes this time around. :-\ Adam Barth wrote: On Feb 7, 2008 4:32 AM, Hallv

Re: [whatwg] Referer header sent with ?

Ian Hickson wrote: This e-mail is a response to all the recent ping="" feedback. I carefully took into account all the feedback mentioned below, as well as past feedback and comments outside these mailing lists. In response to these comments, I've made Referer: be #PING for all pings, and add

Re: [whatwg] SQL storage and onunload

On Fri, 08 Feb 2008 18:24:58 +0100, Brady Eidson <[EMAIL PROTECTED]> wrote: As far as the unload handler question, what are the semantics for XHR? I think the user leaving the page is the same as aborting the download. -- Anne van Kesteren

Re: [whatwg] Significant changes to globalStorage

On Fri, 11 Jan 2008, Dave Camp wrote: > On Dec 10, 2007, at 5:46 PM, Ian Hickson wrote: > > > > I just checked in a change to make globalStorage far simpler -- I > > dropped all the domain manipulation stuff, and made it same-origin > > instead. I also dropped StorageItem and just made the Stora

Re: [whatwg] postMessage: event.source allows navigation of sender

On Feb 7, 2008 4:32 AM, Hallvord R M Steen <[EMAIL PROTECTED]> wrote: > One case I'm still > somewhat concerned about is that one is allowed to set the location of > any top-level window according to the ancestor policy, Yes. I think there is a lot of room for improvement in this part of the navi