<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: fullscreen API coming to browsers near you?</title>
	<atom:link href="http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/feed" rel="self" type="application/rss+xml" />
	<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you</link>
	<description>Cleaning up the web with Ajax</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:55:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2</generator>
	<item>
		<title>By: convivialdingo</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-279103</link>
		<dc:creator>convivialdingo</dc:creator>
		<pubDate>Wed, 24 Feb 2010 05:41:47 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-279103</guid>
		<description>The solution, security wise, is quite simple.  The browser should simple filter all keyboard input except for escape and space.  Additionally a faded popover should inform the user of entering fullscreen, the same as flash.

There would be no ability to type in a password.</description>
		<content:encoded><![CDATA[<p>The solution, security wise, is quite simple.  The browser should simple filter all keyboard input except for escape and space.  Additionally a faded popover should inform the user of entering fullscreen, the same as flash.</p>
<p>There would be no ability to type in a password.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AMIGrAve</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278898</link>
		<dc:creator>AMIGrAve</dc:creator>
		<pubDate>Wed, 17 Feb 2010 09:09:41 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278898</guid>
		<description>Fullscreen API would be wonderful. Personally I&#039;ve been waiting for a kind of kiosk mode standard in browsers but it seems it&#039;s not going to happen. Fullscreen API would is a necessity, even if annoyance avoidance is tough.</description>
		<content:encoded><![CDATA[<p>Fullscreen API would be wonderful. Personally I&#8217;ve been waiting for a kind of kiosk mode standard in browsers but it seems it&#8217;s not going to happen. Fullscreen API would is a necessity, even if annoyance avoidance is tough.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Figaro</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278669</link>
		<dc:creator>Figaro</dc:creator>
		<pubDate>Wed, 03 Feb 2010 02:06:14 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278669</guid>
		<description>Why not follow what the spec says (read octavem&#039;s post): let the user-agent (the browser) provide the fullscreen capability. First the user clicks a button on the video players controls that sets the video element&#039;s to the size of the viewport, and the viewports overflow property is set to hidden. Then the user presses F11, to enter fullscreen browsing mode. The second step could be done first, it doesn&#039;t really matter. If you&#039;re on a site like YouTube, you could remain in fullscreen browsing mode while navigating to other videos.

But this would require the user to not only click the fullscreen button on the video element&#039;s player controls, but then would have to press F11. At least there wouldn&#039;t be a need for the user to be prompted to go to fullscreen mode. However one could argue which is worse, a prompt or a two-step process?

I think that the Web platform should be unobtrusive to the user to begin with (ala Google Chrome). However there will be times when an application, such as a video game, would require the users entire screen. So maybe a fullscreen standard should be taken into consideration.</description>
		<content:encoded><![CDATA[<p>Why not follow what the spec says (read octavem&#8217;s post): let the user-agent (the browser) provide the fullscreen capability. First the user clicks a button on the video players controls that sets the video element&#8217;s to the size of the viewport, and the viewports overflow property is set to hidden. Then the user presses F11, to enter fullscreen browsing mode. The second step could be done first, it doesn&#8217;t really matter. If you&#8217;re on a site like YouTube, you could remain in fullscreen browsing mode while navigating to other videos.</p>
<p>But this would require the user to not only click the fullscreen button on the video element&#8217;s player controls, but then would have to press F11. At least there wouldn&#8217;t be a need for the user to be prompted to go to fullscreen mode. However one could argue which is worse, a prompt or a two-step process?</p>
<p>I think that the Web platform should be unobtrusive to the user to begin with (ala Google Chrome). However there will be times when an application, such as a video game, would require the users entire screen. So maybe a fullscreen standard should be taken into consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pmontrasio</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278636</link>
		<dc:creator>pmontrasio</dc:creator>
		<pubDate>Tue, 02 Feb 2010 09:59:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278636</guid>
		<description>Hitting F11 doesn&#039;t fullscreen the video player. It fullscreens the whole page, which is a different thing. Try F11 on youtube (even the HTML5 version) to appreciate the difference.</description>
		<content:encoded><![CDATA[<p>Hitting F11 doesn&#8217;t fullscreen the video player. It fullscreens the whole page, which is a different thing. Try F11 on youtube (even the HTML5 version) to appreciate the difference.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grayrest</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278625</link>
		<dc:creator>grayrest</dc:creator>
		<pubDate>Tue, 02 Feb 2010 07:43:06 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278625</guid>
		<description>Is hitting F11 really that difficult?</description>
		<content:encoded><![CDATA[<p>Is hitting F11 really that difficult?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hdragomir</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278615</link>
		<dc:creator>hdragomir</dc:creator>
		<pubDate>Tue, 02 Feb 2010 02:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278615</guid>
		<description>A fullscreen API is a must if we&#039;re to replace Flash video players with native, browser video players.

As long as we can only go into fullscreen mode based on some user input ( a click or keystroke ) we should be fine.</description>
		<content:encoded><![CDATA[<p>A fullscreen API is a must if we&#8217;re to replace Flash video players with native, browser video players.</p>
<p>As long as we can only go into fullscreen mode based on some user input ( a click or keystroke ) we should be fine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cyrusomar</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278613</link>
		<dc:creator>cyrusomar</dc:creator>
		<pubDate>Mon, 01 Feb 2010 23:31:17 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278613</guid>
		<description>We keep hitting this problem in browsers. We need to stop coming down on the side of always disallowing behaviors if we want the web platform to be used for real applications.

A simple &quot;This website is requesting to use the full screen. Would you like to allow this?&quot; [Yes/No/Always for youtube.com] is the correct solution for this and any other case where there is potential for abuse of a new capability.</description>
		<content:encoded><![CDATA[<p>We keep hitting this problem in browsers. We need to stop coming down on the side of always disallowing behaviors if we want the web platform to be used for real applications.</p>
<p>A simple &#8220;This website is requesting to use the full screen. Would you like to allow this?&#8221; [Yes/No/Always for youtube.com] is the correct solution for this and any other case where there is potential for abuse of a new capability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: abhijitn</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278611</link>
		<dc:creator>abhijitn</dc:creator>
		<pubDate>Mon, 01 Feb 2010 17:51:54 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278611</guid>
		<description>I don&#039;t know about &#039;make any element in a page display fullscreen&#039;, but in Opera, if I go full screen, the page actually takes up the entire screen; no tabs, no menus, nothing.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know about &#8216;make any element in a page display fullscreen&#8217;, but in Opera, if I go full screen, the page actually takes up the entire screen; no tabs, no menus, nothing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kadams54</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278610</link>
		<dc:creator>kadams54</dc:creator>
		<pubDate>Mon, 01 Feb 2010 16:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278610</guid>
		<description>I&#039;ll second the &quot;if HTML5 video is going to compete with Flash&quot; sentiment, though I&#039;d extend fullscreen mode&#039;s usefulness to Canvas as well. Fullscreen Flash is most useful for games and videos, i.e., Canvas and .

Having a confirmation dialog (&quot;Do you want to allow this site to use your full screen?&quot;) reeks of Windows&#039; UAC. Any security restrictions need to be transparent to the user.</description>
		<content:encoded><![CDATA[<p>I&#8217;ll second the &#8220;if HTML5 video is going to compete with Flash&#8221; sentiment, though I&#8217;d extend fullscreen mode&#8217;s usefulness to Canvas as well. Fullscreen Flash is most useful for games and videos, i.e., Canvas and .</p>
<p>Having a confirmation dialog (&#8220;Do you want to allow this site to use your full screen?&#8221;) reeks of Windows&#8217; UAC. Any security restrictions need to be transparent to the user.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JonathanLeech</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278609</link>
		<dc:creator>JonathanLeech</dc:creator>
		<pubDate>Mon, 01 Feb 2010 16:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278609</guid>
		<description>It would be funny if something like this forced Safari to support full screen browsing.</description>
		<content:encoded><![CDATA[<p>It would be funny if something like this forced Safari to support full screen browsing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SteveElbows</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278608</link>
		<dc:creator>SteveElbows</dc:creator>
		<pubDate>Mon, 01 Feb 2010 16:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278608</guid>
		<description>Well fullscreen video capability is probably a must if html5 video is to compete effectively with flash, but beyond that Im not so sure - ok probably webGL also needs a fullscreen capability.</description>
		<content:encoded><![CDATA[<p>Well fullscreen video capability is probably a must if html5 video is to compete effectively with flash, but beyond that Im not so sure &#8211; ok probably webGL also needs a fullscreen capability.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IEUCActual</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278607</link>
		<dc:creator>IEUCActual</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278607</guid>
		<description>I think a bottom left corner icon would be a good visual cue, also I think tasteful alternate CSS Cursors applied with User Style Sheet priority would be a good idea. Then we could have text input enabled with a custom cursor that would let End Users see they were interacting with a full screen web page generated dialog. The custom cursors would need to be recognizable across platforms (in case the full screen application was deployed to drive information kiosks running heterogeneous configurations) and could consist of the standard cursors combined with an asterisk or some other platform independent annotation mark.</description>
		<content:encoded><![CDATA[<p>I think a bottom left corner icon would be a good visual cue, also I think tasteful alternate CSS Cursors applied with User Style Sheet priority would be a good idea. Then we could have text input enabled with a custom cursor that would let End Users see they were interacting with a full screen web page generated dialog. The custom cursors would need to be recognizable across platforms (in case the full screen application was deployed to drive information kiosks running heterogeneous configurations) and could consist of the standard cursors combined with an asterisk or some other platform independent annotation mark.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anjanb</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278604</link>
		<dc:creator>anjanb</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:36:30 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278604</guid>
		<description>hi there,

  would love a FULL SCREEN API. cool.

BR,
~A</description>
		<content:encoded><![CDATA[<p>hi there,</p>
<p>  would love a FULL SCREEN API. cool.</p>
<p>BR,<br />
~A</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joeri</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278601</link>
		<dc:creator>Joeri</dc:creator>
		<pubDate>Mon, 01 Feb 2010 15:28:57 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278601</guid>
		<description>An important aspect of full-screen mode in flash is that users can&#039;t enter text while they are in full-screen mode, so evil sites won&#039;t trick them into entering their password. If you take away the ability of entering text (and really, you should), aside from video there&#039;s simple not much use to full-screen mode.</description>
		<content:encoded><![CDATA[<p>An important aspect of full-screen mode in flash is that users can&#8217;t enter text while they are in full-screen mode, so evil sites won&#8217;t trick them into entering their password. If you take away the ability of entering text (and really, you should), aside from video there&#8217;s simple not much use to full-screen mode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jnbdz</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278600</link>
		<dc:creator>jnbdz</dc:creator>
		<pubDate>Mon, 01 Feb 2010 14:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278600</guid>
		<description>I think that the browser should ask permission to the user, to use full screen.

EX:

Do you want to have this site use your full screen.

(Yes) (No) (I don&#039;t know)

And you get the full screen you get something like in flash that says you only need to click on esc on your keyboard to get ride of the full screen.

We could also see in the corner of the screen a small icon that shows that your full screen. And it would be impossible to remove or to hide.

Does are my solutions to the security problem.</description>
		<content:encoded><![CDATA[<p>I think that the browser should ask permission to the user, to use full screen.</p>
<p>EX:</p>
<p>Do you want to have this site use your full screen.</p>
<p>(Yes) (No) (I don&#8217;t know)</p>
<p>And you get the full screen you get something like in flash that says you only need to click on esc on your keyboard to get ride of the full screen.</p>
<p>We could also see in the corner of the screen a small icon that shows that your full screen. And it would be impossible to remove or to hide.</p>
<p>Does are my solutions to the security problem.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RoryH</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278599</link>
		<dc:creator>RoryH</dc:creator>
		<pubDate>Mon, 01 Feb 2010 13:56:42 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278599</guid>
		<description>Just use the same model as Flash where the fullScreen event can only be activated via a user click event... NEVER allow full screen adhoc from the code.</description>
		<content:encoded><![CDATA[<p>Just use the same model as Flash where the fullScreen event can only be activated via a user click event&#8230; NEVER allow full screen adhoc from the code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: gossi</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278598</link>
		<dc:creator>gossi</dc:creator>
		<pubDate>Mon, 01 Feb 2010 13:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278598</guid>
		<description>I would love to have the option giving Fullscreen-Mode to a specific element, keep going :)</description>
		<content:encoded><![CDATA[<p>I would love to have the option giving Fullscreen-Mode to a specific element, keep going :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WillPeavy</title>
		<link>http://ajaxian.com/archives/fullscreen-api-coming-to-browsers-near-you/comment-page-1#comment-278597</link>
		<dc:creator>WillPeavy</dc:creator>
		<pubDate>Mon, 01 Feb 2010 13:35:43 +0000</pubDate>
		<guid isPermaLink="false">http://ajaxian.com/?p=8514#comment-278597</guid>
		<description>Would be a nice feature if used responsibly, but it seems there is a lot of potential for misuse. HTML 5 could become a world of full-screen pop-up ads.</description>
		<content:encoded><![CDATA[<p>Would be a nice feature if used responsibly, but it seems there is a lot of potential for misuse. HTML 5 could become a world of full-screen pop-up ads.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

