Re: [whatwg] Fullscreen and non-HTML elements

2012-04-09 Thread Ian Hickson
On Mon, Apr 9, 2012 at 4:58 AM, Charles McCathieNevile wrote: > On Fri, 06 Apr 2012 16:51:30 +0200, Anne van Kesteren > wrote: > > On Fri, 06 Apr 2012 16:25:20 +0200, Doug Schepers >> wrote: >> >>> What's the rationale for restricting what authors (or users) can make >>> fullscreen? >>> >> >> Y

Re: [whatwg] Fullscreen and non-HTML elements

2012-04-09 Thread Charles McCathieNevile
On Fri, 06 Apr 2012 16:51:30 +0200, Anne van Kesteren wrote: On Fri, 06 Apr 2012 16:25:20 +0200, Doug Schepers wrote: What's the rationale for restricting what authors (or users) can make fullscreen? You cannot render arbitrary SVG elements without a root element as far as I know.

Re: [whatwg] Fullscreen and non-HTML elements

2012-04-06 Thread Ian Hickson
On Fri, 6 Apr 2012, Anne van Kesteren wrote: > > The other day I was wondering whether I should change Fullscreen to not be > applicable to all elements. I was thinking HTMLElement and SVGSvgElement > () would probably be best. My reasoning was that it will not work for > and such. There's plent

Re: [whatwg] Fullscreen and non-HTML elements

2012-04-06 Thread Anne van Kesteren
On Fri, 06 Apr 2012 16:25:20 +0200, Doug Schepers wrote: What's the rationale for restricting what authors (or users) can make fullscreen? You cannot render arbitrary SVG elements without a root element as far as I know. -- Anne van Kesteren http://annevankesteren.nl/

[whatwg] Fullscreen and non-HTML elements

2012-04-06 Thread Anne van Kesteren
Hey, The other day I was wondering whether I should change Fullscreen to not be applicable to all elements. I was thinking HTMLElement and SVGSvgElement () would probably be best. My reasoning was that it will not work for and such. Just now I noticed https://bugzilla.mozilla.org/show_bu