Re: [whatwg] HttpOnly cookie for WebSocket?

2010-02-01 Thread Ian Hickson
On Thu, 28 Jan 2010, Fumitoshi Ukai (��~\飼�~V~G�~U~O) wrote: May/Should WebSocket use HttpOnly cookie while Handshaking? I think it would be useful to use HttpOnly cookie on WebSocket so that we could authenticate the WebSocket connection by the auth token cookie which might be HttpOnly

Re: [whatwg] api for fullscreen() - security issues

2010-02-01 Thread Henri Sivonen
On Jan 31, 2010, at 05:08, Simon Fraser wrote: * disallow enterFullscreen() from a frame or iframe This might be a problem if video sites transition their embedding boilerplate to an iframe in order to be able to be able to serve HTML5, Flash, ActiveX, etc. depending on UA without requiring

Re: [whatwg] api for fullscreen() - security issues

2010-02-01 Thread Simon Fraser
On Feb 1, 2010, at 1:14 AM, Henri Sivonen wrote: On Jan 31, 2010, at 05:08, Simon Fraser wrote: * disallow enterFullscreen() from a frame or iframe This might be a problem if video sites transition their embedding boilerplate to an iframe in order to be able to be able to serve HTML5,

Re: [whatwg] Codecs for audio and video

2010-02-01 Thread Chris McCormick
On Sun, Aug 09, 2009 at 08:29:28PM +1000, Silvia Pfeiffer wrote: On Sun, Aug 9, 2009 at 7:20 PM, Chris McCormickch...@mccormick.cx wrote: Hi Sylvia, On Sun, Aug 09, 2009 at 11:16:01AM +1000, Silvia Pfeiffer wrote: On Sun, Aug 9, 2009 at 3:15 AM, Chris McCormickch...@mccormick.cx wrote:

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Henry Bridge
The enableKeys parameter to enterFullscreen is a hint to the UA that the application would like to be able to receive arbitrary keyboard input. Otherwise the UA is likely to disable alphanumeric keyboard input. If enableKeys is specified, the UA might require more severe confirmation UI.

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Kenneth Russell
On Thu, Jan 28, 2010 at 8:55 PM, Robert O'Callahan rob...@ocallahan.org wrote: On Fri, Jan 29, 2010 at 5:06 PM, Geoff Stearns tensafefr...@google.com wrote: enterFullscreen always returns immediately. If fullscreen mode is currently supported and permitted, enterFullscreen dispatches a task

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Robert O'Callahan
On Tue, Feb 2, 2010 at 7:39 AM, Kenneth Russell k...@google.com wrote: When you say that the DOM viewport of the element is aligned with the screen when it goes fullscreen, does that mean that the .width and .height properties are changed? Or does it mean that the element's size is changed by

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Kenneth Russell
On Mon, Feb 1, 2010 at 11:05 AM, Robert O'Callahan rob...@ocallahan.org wrote: On Tue, Feb 2, 2010 at 7:39 AM, Kenneth Russell k...@google.com wrote: When you say that the DOM viewport of the element is aligned with the screen when it goes fullscreen, does that mean that the .width and

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Brian Campbell
On Jan 28, 2010, at 9:42 PM, Robert O'Callahan wrote: enterFullscreen always returns immediately. If fullscreen mode is currently supported and permitted, enterFullscreen dispatches a task that a) imposes the fullscreen style, b) fires the beginfullscreen event on the element and c)

Re: [whatwg] Codecs for audio and video

2010-02-01 Thread Silvia Pfeiffer
On Tue, Feb 2, 2010 at 4:05 AM, Chris McCormick ch...@mccormick.cx wrote: On Sun, Aug 09, 2009 at 08:29:28PM +1000, Silvia Pfeiffer wrote: On Sun, Aug 9, 2009 at 7:20 PM, Chris McCormickch...@mccormick.cx wrote: Hi Sylvia, On Sun, Aug 09, 2009 at 11:16:01AM +1000, Silvia Pfeiffer wrote:

Re: [whatwg] api for fullscreen() - security issues

2010-02-01 Thread Robert O'Callahan
On Tue, Feb 2, 2010 at 5:00 AM, Simon Fraser s...@me.com wrote: On Feb 1, 2010, at 1:14 AM, Henri Sivonen wrote: On Jan 31, 2010, at 05:08, Simon Fraser wrote: * disallow enterFullscreen() from a frame or iframe This might be a problem if video sites transition their embedding

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Robert O'Callahan
On Tue, Feb 2, 2010 at 10:41 AM, Brian Campbell lam...@continuation.orgwrote: I'm a bit concerned about when the fullscreen events and styles apply, though. If the page can tell whether or not the user has actually allowed it to enter fullscreen mode, it can refuse to display content until the

[whatwg] Websocket algorithmic specification

2010-02-01 Thread Greg Wilkins
Sorry for the cross post hybi/whatwg. I raised these issues on hybi list, but there was no specific response (probably due to the other issues being debated there). I think the issues below indicate ambiguities in the spec. I raised them as an argument to change away from the algorithmic style

Re: [whatwg] Codecs for audio and video

2010-02-01 Thread David Singer
On Feb 1, 2010, at 14:02 , Silvia Pfeiffer wrote: On Tue, Feb 2, 2010 at 4:05 AM, Chris McCormick ch...@mccormick.cx wrote: I think I speak for all procedural audio people when I say, can't we get the browsers to allow sample-block access to audio? Sounds like a solid argument to me. But

Re: [whatwg] api for fullscreen()

2010-02-01 Thread Brian Campbell
On Feb 1, 2010, at 5:38 PM, Robert O'Callahan wrote: On Tue, Feb 2, 2010 at 10:41 AM, Brian Campbell lam...@continuation.org wrote: I'm a bit concerned about when the fullscreen events and styles apply, though. If the page can tell whether or not the user has actually allowed it to enter

Re: [whatwg] Codecs for audio and video

2010-02-01 Thread Chris Double
On 02/02/10 06:05, Chris McCormick wrote: I think I speak for all procedural audio people when I say, can't we get the browsers to allow sample-block access to audio? Dave Humphrey has been working on adding an API to do this to Firefox. He's been blogging about it here: