(This e-mail only contains responses to the one brief part of the full-
screen API feedback that apply to the spec(s) I'm working on; I believe
Anne has stated an intent to specify an API for actually supporting
fullscreen display of Web content and I have not responded to feedback
that would
On Mon, Aug 23, 2010 at 5:25 PM, Adam Barth w...@adambarth.com wrote:
So... The trade-off is:
1) Only browsing contexts can go full-screen (since they have URLs
that we could display).
2) Any element can go full-screen, but we'll need to add a nasty
non-semantic attribute.
Is
On Sun, Aug 22, 2010 at 4:12 AM, Adam Barth w...@adambarth.com wrote:
On Sat, Aug 21, 2010 at 2:00 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Sat, Aug 21, 2010 at 5:21 PM, Adam Barth w...@adambarth.com wrote:
How is going fullscreen different from opening a popup window?
That
On Sun, Aug 22, 2010 at 8:00 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Sun, Aug 22, 2010 at 4:12 AM, Adam Barth w...@adambarth.com wrote:
On Sat, Aug 21, 2010 at 2:00 AM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Sat, Aug 21, 2010 at 5:21 PM, Adam Barth w...@adambarth.com
On Mon, Aug 23, 2010 at 3:46 PM, Adam Barth w...@adambarth.com wrote:
Yeah, I agree that we'd need something like that in this model. It's
unfortunate though. Won't folks package video widgets using
iframes? I guess they'll need to include this silly attribute in
their copy-and-paste this
On Sun, Aug 22, 2010 at 9:39 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Sun, Aug 22, 2010 at 8:00 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Sun, Aug 22, 2010 at 4:12 AM, Adam Barth w...@adambarth.com wrote:
This doesn't seem like a good model for full-screen. I would
On Mon, Aug 23, 2010 at 4:42 PM, Adam Barth w...@adambarth.com wrote:
Oh, I think the iframe-at-a-time is an easier model to work with since
the scripting context will get adopted into the full-screen view
together with the elements.
It requires the author to put each part of their page that
On Sun, Aug 22, 2010 at 9:56 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Mon, Aug 23, 2010 at 4:42 PM, Adam Barth w...@adambarth.com wrote:
Oh, I think the iframe-at-a-time is an easier model to work with since
the scripting context will get adopted into the full-screen view
together
On Mon, Aug 23, 2010 at 5:03 PM, Adam Barth w...@adambarth.com wrote:
On Sun, Aug 22, 2010 at 9:56 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Mon, Aug 23, 2010 at 4:42 PM, Adam Barth w...@adambarth.com wrote:
Oh, I think the iframe-at-a-time is an easier model to work with since
On Sun, Aug 22, 2010 at 10:11 PM, Robert O'Callahan
rob...@ocallahan.org wrote:
On Mon, Aug 23, 2010 at 5:03 PM, Adam Barth w...@adambarth.com wrote:
On Sun, Aug 22, 2010 at 9:56 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Mon, Aug 23, 2010 at 4:42 PM, Adam Barth w...@adambarth.com
On Fri, Aug 20, 2010 at 10:24 PM, Kit Grose k...@iqmultimedia.com.au wrote:
On 21/08/2010, at 3:21 PM, Adam Barth wrote:
On Fri, Aug 20, 2010 at 7:25 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Sat, Aug 21, 2010 at 8:24 AM, Ian Hickson i...@hixie.ch wrote:
One comment: Rather than
On Sat, Aug 21, 2010 at 5:21 PM, Adam Barth w...@adambarth.com wrote:
How is going fullscreen different from opening a popup window?
That depends on how the UA chooses to handle it. But this proposed
fullscreen API is based on the idea that the fullscreen content takes over
the toplevel
On Sat, Aug 21, 2010 at 2:00 AM, Robert O'Callahan rob...@ocallahan.org wrote:
On Sat, Aug 21, 2010 at 5:21 PM, Adam Barth w...@adambarth.com wrote:
How is going fullscreen different from opening a popup window?
That depends on how the UA chooses to handle it. But this proposed
fullscreen API
Controlling the rendering of content, e.g. as being full-screen or not, is
a presentation-specific concern (e.g. it doesn't even apply to a speech-
based browser, with no loss of features to the user), so the right place
to specify it is something like CSSOM, not HTML. Thus, I haven't added
On Aug 20, 2010, at 3:24 PM, Ian Hickson wrote:
By CSSOM, I mean a separate specification, specifically one from the
family of specifications that Anne is working on
...though my understanding is that Anne doesn't have the bandwidth to take
this on right now (this may be less of a problem if
On Sat, Aug 21, 2010 at 8:24 AM, Ian Hickson i...@hixie.ch wrote:
One comment: Rather than adding an allowfullscreen attribute on
iframe, I would suggest just assuing that sandboxed content (i.e.
content of iframes with the sandbox= attribute) can't go fullscreen. I
can provide a sandbox flag
On Sat, 21 Aug 2010, Robert O'Callahan wrote:
On Sat, Aug 21, 2010 at 8:24 AM, Ian Hickson i...@hixie.ch wrote:
One comment: Rather than adding an allowfullscreen attribute on
iframe, I would suggest just assuing that sandboxed content (i.e.
content of iframes with the sandbox=
On Fri, Aug 20, 2010 at 7:25 PM, Robert O'Callahan rob...@ocallahan.org wrote:
On Sat, Aug 21, 2010 at 8:24 AM, Ian Hickson i...@hixie.ch wrote:
One comment: Rather than adding an allowfullscreen attribute on
iframe, I would suggest just assuing that sandboxed content (i.e.
content of iframes
On 21/08/2010, at 3:21 PM, Adam Barth wrote:
On Fri, Aug 20, 2010 at 7:25 PM, Robert O'Callahan rob...@ocallahan.org
wrote:
On Sat, Aug 21, 2010 at 8:24 AM, Ian Hickson i...@hixie.ch wrote:
One comment: Rather than adding an allowfullscreen attribute on
iframe, I would suggest just assuing
19 matches
Mail list logo
