Native Fullscreen JavaScript API (plus jQuery plugin)

October 20, 2011 | JavaScript | 91 Comments

HTML5 <video> is great, but when it was first released, one of the big complaints was that it couldn’t do true FullScreen like Flash. Thankfully, this is changing and native FullScreen support is coming to most browsers in the next few months (no word from the Internet Explorer team Update on IE below #5))

The API is still heavily in flux especially since the W3C joined in this week. I spent some time working through the differences to implement FullScreen in MediaElement.js HTML5 video player, and it’s working great in Safari 5.1+, Chrome Canary Chrome 15+, or Firefox Nightly (go to about:config and set full-screen-api.enabled= true) and scheduled for Firefox 10. Below I’m going to try to explain how things evolved, where we are today, and then some code that you can play with.

Simple Demo Video Demo

A Brief History of the FullScreen API

  1. The first native FullScreen implementation appeared in Safari 5.0 (and iOS) added a a webkitEnterFullScreen() function that only worked on <video> tags using Safari’s video controls (see Apple’s HTML5VideoElement).
  2. For Safari 5.1, Apple changed the API to be more inline with Mozilla’s FullScreen API proposal (which actually predates Apple’s implementation). Now, webkitRequestFullScreen() can be called on any DOM element which makes that portion of an HTML page go fullscreen.
  3. Firefox and Chrome announced that they will add FullScreen API support, and the feature has already arrived in Chrome Canary Chrome 15+ and Firefox Nightly (scheduled for Firefox 10). The Mozilla team has posted some a demo.
  4. On October 15, 2011, the W3C released a Fullscreen API proposal (written by a member of the Opera team) which has two main differences from Mozilla’s proposal:
    1. Mozilla/Webkit uses a Capital ‘S’ (FullScreen) while W3C does not (Fullscreen)
    2. Mozilla/Webkit uses cancelFullScreen
      while W3C uses exitFullscreen
  5. Update (11/15/2011): Ted Johnson from IEBlog says IE10 will not support the FullScreen API (12/05/2011: I misunderstood the first email from Ted) that the IE10 team has not yet decided whether to implement the FullScreen API. He notes however that, “Windows 8 Metro style Internet Explorer is always full screen … and as before, F11 enters full screen mode in desktop versions of IE.”

Understanding the FullScreen API

Here are the most important parts of the FullScreen API with notes on how things differ among browsers. In general, I’m using the Mozilla/Webkit spelling in the examples below, but I’m also noting the W3C differences where needed.

1. Detecting FullScreen support

To detect fullscreen support, you’ll need to use the typeof command to find out if a given browser has support for the FullScreen API methods. There is also boolean property called fullScreenEnabled that tells you if the user has disabled the feature (strangely WebKit does not have the fullScreenEnabled property making it difficult to detect if it’s turned off).

// Mozilla's proposed API: in practice, you'll need vendor prefixes (see examples below)
if (typeof document.cancelFullScreen != 'undefined' && document.fullScreenEnabled === true) {
    /* do fullscreen stuff */

2. Entering and Exiting FullScreen

To enter FullScreen mode, you call requestFullScreen (or requestFullscreen for W3C) on the element want to be viewed in FullScreen. To exit you call cancelFullScreen (or exitFullscreen for W3C) on the document object.

// mozilla proposal

// Webkit (works in Safari and Chrome Canary)

// Firefox (works in nightly)

// W3C Proposal

Mozilla has also proposed an alternate requestFullScreenWithKeys() method which would enable the user to use the keyboard in FullScreen mode. With Flash, Adobe always disabled keyboard support in FullScreen to prevent malicious sites from attempting to steal passwords, but it looks like the browser makers are considering making this an option.

3. Fullscreen Event and Current Status

To detect when a FullScreen event happens, there is a fullscreeneventchange that fires on the element going FullScreen and a boolean property (fullScreen) on the document object that reports if it’s in FullScreen mode or not.

element.addEventListener('fullscreeneventchange', function(e) {
    if (document.fullScreen) {
       /* make it look good for fullscreen */
    } else {
       /* return to the normal state in page */
}, true);

// note: unlike Webkit and the W3C proposal, 
// Mozilla fires its mozfullscreenchange event on the *document* object
// instead of the element going fullscreen

Mozilla also mentions the possibility of adding a fullscreendenied event in the future. You should also know that Webkit added an ‘Is’ to their boolean property and that the W3C proposal strangely does not include this property:

// Mozilla proposal
// Firefox (Nightly)
// Webkit (Chrome, Safari)
document.webkitIsFullScreen; // note the 'Is'
// W3C proposal
// None? Why?

4. Styling FullScreen

Both Mozilla and the W3C have proposed new pseudo CSS classes for styling elements in FullScreen mode.

/* normal state */
.my-container {
    width: 640px;
    height: 360px;

/* Mozilla proposal (dash) */
.my-container:full-screen {

/* W3C proposal (no dash) */
.my-container:fullscreen {

/* currently working vendor prefixes */
.my-container:-webkit-full-screen, .my-container:-moz-full-screen {

5. Embedding FullScreen

When you embed content from another site (like a YouTube video) using Flash’s <object><embed> tags, you can specificy whether or not to allow FullScreen to work. This feature has also been added to the <iframe> tag using the allowFullScreen attribute.

<!-- content from another site that is allowed to use the fullscreen command -->
<iframe src="" width="640" height="360" allowFullScreen></iframe>

Putting it All Together

To make this work in its current state, you need a wrapper that can help detect the right features. Here’s what I’ve put together to work in Safari 5.1, Chrome Canary Chrome 15+, and Firefox Nightly. I’ll update it if the W3C notation goes through:

(function() {
		fullScreenApi = {
			supportsFullScreen: false,
			isFullScreen: function() { return false; },
			requestFullScreen: function() {},
			cancelFullScreen: function() {},
			fullScreenEventName: '',
			prefix: ''
		browserPrefixes = 'webkit moz o ms khtml'.split(' ');

	// check for native support
	if (typeof document.cancelFullScreen != 'undefined') {
		fullScreenApi.supportsFullScreen = true;
	} else {
		// check for fullscreen support by vendor prefix
		for (var i = 0, il = browserPrefixes.length; i < il; i++ ) {
			fullScreenApi.prefix = browserPrefixes[i];

			if (typeof document[fullScreenApi.prefix + 'CancelFullScreen' ] != 'undefined' ) {
				fullScreenApi.supportsFullScreen = true;


	// update methods to do something useful
	if (fullScreenApi.supportsFullScreen) {
		fullScreenApi.fullScreenEventName = fullScreenApi.prefix + 'fullscreenchange';

		fullScreenApi.isFullScreen = function() {
			switch (this.prefix) {
				case '':
					return document.fullScreen;
				case 'webkit':
					return document.webkitIsFullScreen;
					return document[this.prefix + 'FullScreen'];
		fullScreenApi.requestFullScreen = function(el) {
			return (this.prefix === '') ? el.requestFullScreen() : el[this.prefix + 'RequestFullScreen']();
		fullScreenApi.cancelFullScreen = function(el) {
			return (this.prefix === '') ? document.cancelFullScreen() : document[this.prefix + 'CancelFullScreen']();

	// jQuery plugin
	if (typeof jQuery != 'undefined') {
		jQuery.fn.requestFullScreen = function() {

			return this.each(function() {
				if (fullScreenApi.supportsFullScreen) {

	// export api
	window.fullScreenApi = fullScreenApi;

This creates an object called fullScreenApi with a boolean property supportsFullScreen and some methods that allow you to do something more universal. Here’s an example usage:

if (fullScreenApi.supportsFullScreen) {
	myButton.addEventListener('click', function() {
	}, true);

You can see it in action below:

Simple Demo Video Demo

Issues and Updates

Since this post, there are some additional things worth mentioning

  • Security concerns – Browser vendors are well aware of the potential security issues with fullscreen. For example, a malicious site could show a full screen Windows or Mac login window and steal a password. That’s why they are disabling keyboard support by default and only enabling by explicitly asking.
  • Internet Explorer supportI have an email from a IE team member saying they are discussing it, but have not made any decisions. As of now, IE10 will not implement the FullScreen API, the IE team has not yet decided if they will implement the FullScreen API.
  • FullscreenEnabled vs. IsFullScreen – The W3C includes the very helpful fullscreenEnabled flag to let your code know if you can use the API, but strangely the W3C does not include an isFullscreen flag. WebKit on the other hand has webkitIsFullScreen, but does not have a webkitFullScreenEnabled equivalent property. Mozilla helpfully includes both.
  • FullScreenChanged event – The W3C and Webkit fire the fullscreenchanged event on the element going fullscreen, but Mozilla fires the event on the document object.

91 responses to “Native Fullscreen JavaScript API (plus jQuery plugin)”

  1. LockeVN says:

    End-user Chrome version 15.0.874.102 m is now support FullScreen API, and this code works!

  2. […] Native Fullscreen JavaScript API (plus jQuery plugin); […]

  3. Jordan says:

    It doesn’t appear that the simple demo works while testing in Firefox Nightly. Is this a feature that needs to be turned on? Feature detect was successful however.

    • johndyer says:

      I’ve only tested on a Mac, but my Firefox Nightly is still working. What does yours do?

    • Daniel Johansson says:

      Make sure you’ve enabled it in about:config.
      Just search for “full-screen-api.enabled” and set it to true! 🙂

      (btw the labels in this for are very confusingly positioned. I see them below the actual field and with plenty of room between)

  4. Mentifex says:

    The FullScreen option is very important in a serious JavaScript application, especially something like the artificial intelligence for Microsoft Internet Explorer, which in the User Manual simply advises users to press the “function key F11 at the top of your keyboard to toggle or alternate between a full-screen display and the normal screen of Microsoft Internet Explorer (MSIE).”

  5. […] 2, 2011 Just a quick note for you. If you’re into web app development, this might be an interesting read. It’s on using JavaScript to make pages fullscreen, hiding the browser chrome and making your […]

  6. Nice article, thought you’d appreciate some updates:

    1) document.fullscreen has been depricated in the W3C proposal due to similarity to document.fullscreenElement
    Note: document.fullscreen was a boolean, whereas document.fullscreenElement is either a string (current fullscreen element) or undefined. This has no effect for the time being, as the draft is not implemented, however it will effect the future.

    2) It is also worth mentioning the “@media (view-type: fullscreen)” draft. Currently supported in only Opera (I think).
    This, I think, allows you to style any element for when the document is in fullscreen mode. It also allows you to take advantage of when the user hits F11.
    @media (view-type: fullscreen) {
    div#videoContainer {
    video {

    • johndyer says:

      Thanks Matt! I’m not sure I understand why W3C doesn’t have a fullscreen state flag like Webkit and Mozilla. Hopefully, it’ll become clearer as they work out the kinks.

    • Marcus Tucker says:

      The ability to specify fullscreen styling via @media is exactly what’s needed, thanks for making us aware of it – and it would be utter madness if W3C didn’t incorporate it!

  7. David says:

    It’s worth noting that the specification was not proposed with differences out of the blue. That draft of the spec was discussed at the WHATWG with other browser vendors. It’s likely still under development too. See the many threads here.

    • johndyer says:

      Thanks David. I emailed Anne, and she said they were still working on it. But to me it still seems strange to be so out of sync from the Mozilla proposal and Apple implementation since those have been out so long…

  8. Chris Pearce says:

    Document.fullScreenEnabled also returns false if any of the document’s containing iframes don’t have the “allowfullscreen” attribute present. You can use this in custom video controls embedded in an iframe to determine whether it’s worthwhile showing the full-screen button in your controls. And in Firefox at least it also returns false if there’s a windowed plugin present in any of the full-screen documents.

    The “fullscreendenied” event has been named to “fullscreenerror” in the W3C spec, and support for it as the “mozfullscreenerror” event landed in Firefox yesterday, and will appear in nightly builds tomorrow.

  9. Nick says:

    So i’m a bit confused, can’t I just do a simple one liner in jquery to get this to put the document into fullscreen(same as if I pressed f-11 in Chrome?


    Is it possible to do it in a nice little compact way like this, instead of the plugin you made?

    • johndyer says:

      Yes, you could do a one-liner, but right now the browsers are all using vendor prefixes and the API is set to change which means your code might not be future proof if you don’t wrap it in something that can mitigate the changes.

  10. […] Your Content Do the Talking: Fullscreen API 2. 大部分代码引用这篇文章:Native Fullscreen JavaScript API (plus jQuery plugin) 3. 历史和讨论:Fullscreen HTML5 video 4. 标准与厂商对比:W3C Draft: Fullscreen […]

  11. […] I hope you enjoyed my post. Some facts and code examples I've taken from another blog, so I would like to add this as a source. […]

  12. Marcus Tucker says:

    Would be nice to add Fullscreen detection to Modernizr, is anyone already on the case or shall I suggest it?

  13. Marc says:

    How does this handle dual screens? Is it possible to use two or three screens simultaneously?

  14. “Windows 8 Metro style Internet Explorer is always full screen … and as before, F11 enters full screen mode in desktop versions of IE.”

    Not really helpful when you need to go full-screen from an embedded source like an iframe, as we do for our embedded html video player at Vimeo. Guess IE users will continue getting the shaft (ie. have to use Flash, which is not even an option in Metro).

  15. Marco Campos says:

    and what about opera? does it suport fullscreen?

    we could simulate a F11 keypress on IE or it don’t work?

  16. ariok says:

    it’s possible to default chrome into fullscreen every open it?

  17. […] from my program? Answer (Unmark) 12/15/11 1:45 PM as a reply to ivanov -void. Hi,maybe this helps […]

  18. Knotschi says:

    in line 66 you have : fullScreenApi.requestFullScreen(el);
    that have to be: fullScreenApi.requestFullScreen(el[0]);


  19. pixluser says:

    Thanks for this nice script ! It’s perfect for jquery slideshow, but what about normal pages ? I can’t get a scrollbar there, it’s impossible to scrolldown inside a long div… do you know why ? Thanks in advance !!

  20. fimbim says:

    Pretty nice. I don´t think that many users will actually click on “fullscreen” unless they wanne watch a movie or really hd images… Therefor it´s perfect. Thanks for sharing!

  21. […] 浏览 →首页快报创业公司信息图评论推荐36氪开放日 Abner Tsang 发表于 下午 10:00/*0){$('#t_sina_btn').html('');$('#author_weibo').html('');$('#weibo_cmtbox').html('');}});/*]]>*/ 1 次评论HTML5全屏来袭:支持浏览器原生全屏的JavaScript代码发布前两天我们报道了最新发布的FireFox 10开始支持全屏API。可能很多人暂时不清楚能把这个全屏API用在什么地方,但是已经有人把调用这个功能的JavaScript代码发布出来,并且已经能与HTML5的“video”标签组合应用。在这个jQuery插件的主页上,发布了一个全屏演示和一个应用“video”标签的视频演示。同时提醒除FireFox 10外,仅Chrome 15与Safari 5.1或更高版本的浏览器支持原生全屏API。也就是说,你的浏览器版本不满足这个条件,可就不能正常运行这个功能。目前所有的IE浏览器都暂不支持,该Demo在检测出来后会给你相应提示。经测试,首次运行全屏Demo时浏览器会出现一个浏览器的授权提示,在你允许后下次再运行就不会再出现。Demo在全屏后只能按“ESC”键退出,在页面中没有显示或隐藏的退出全屏接口,在代码的实际应用时建议还是加上。如果浏览器支持HTML5,你应该可以看到下面这段视频。如果同时还是上述版本的浏览器,可以试着将其全屏播放。需要再次提醒的是,这段视频由“video”标签载入,而非Flash。另外再附上一段“audio”标签加载的音频。 native感兴趣的朋友可以去他们的网站了解详情,或者是去GitHub查看实现全屏的JavaScript代码。视频和音频标签相关的内容在这里。 […]

  22. […] Firefox10发布一项重要更新开放了全屏API,这意味着未来会出现真正全屏运行的HTML5应用,例如与video标签结合,实现全屏播放视频而摆脱对Flash的依赖。 目前该功能仅限于Firefox10,Chrome15或Safari5.1及更高版本,在目前全部IE版本下无法运行。目前有一jQuery插件MediaElement已经结合HTML5全屏API与video/audio标签实现了全屏播放,这里有该作者发布的全屏演示。 Posted in: W3C and F2E, jQuery HTML5 /* […]

  23. […] 在这个jQuery插件的主页上,发布了一个全屏演示和一个应用“video”标签的视频演示。同时提醒除FireFox 10外,仅Chrome 15与Safari 5.1或更高版本的浏览器支持原生全屏API。也就是说,你的浏览器版本不满足这个条件,可就不能正常运行这个功能。目前所有的IE浏览器都暂不支持,该Demo在检测出来后会给你相应提示。 […]

  24. kailuo wang says:

    Great article! Full those who are interested in keyboard support under fullscreen mode, in webkit you can do
    webkitRequestFullScreen(Element.ALLOW_KEYBOARD_INPUT), then you have full keyboard support.
    For firefox, by default, the keyboard is allowed, but most key will also initiate the “press ESC to exit full screen” popup (which is rather huge), I didn’t find a way to disable that.

  25. meizhitao says:

    Hello, I have met a question :
    I want the web page to be initialized fullscreen, So I use the following code :

    But it didn’t go as expected !

    Is there any solutions , or there was bugs in my code ? Thanks !

  26. […] 在这个jQuery插件的主页上,发布了一个全屏演示和一个应用“video”标签的视频演示。同时提醒除FireFox 10 外,仅Chrome 15与Safari 5.1或更高版本的浏览器支持原生全屏API。也就是说,你的浏览器版本不满足这个条件,可就不能正常运行这个功能。目前所有的IE浏览器都暂不支持,该Demo在检测出来后会给你相应提示。 […]

  27. […] 本文翻译自《Native Fullscreen JavaScript API (plus jQuery plugin) 》,略有删改。 分类: html5 标签: 全屏 评论 (0) Trackbacks (0) 发表评论 Trackback […]

  28. Neat! I forked and modified it a bit to not put any identifiers in the global namespace, and integrate more naturally with jQuery:

    Poke me if you strongly feel it should have some more restrictive license, inline attribution or similar.

  29. Worth noting, by the way – to use the API inside of an iframe, you currently need to slap on all the vendor prefixes in the iframe tag attributes too, i e something like: <iframe src=”url” allowfullscreen mozallowfullscreen webkitallowfullscreen oallowfullscreen msallowfullscreen> (to be sure all browsers will allow the API, if / once they implement it).

  30. DearMrMiller says:

    Having implemented this API there are couple of things I’ve noticed that aren’t well documented elsewhere. This may not pertain to every implementation but it did to mine and may help some folks:

    1. Loading a new page in Firefox will take you out of fullscreen unless you’re using asynchronous JavaScript to load new images or what have you. In the site I was constructing this wasn’t really feasible so I removed the fullscreen ability from Firefox which to me was a minor issue as it’s an ‘added bonus’ not core functionality. However in Safari / Chrome it will remain in fullscreen when you navigate to new pages.

    2. If you’re using fullscreen to navigate to new pages in Safari / Chrome there is no way to indicate that you’re still in fullscreen. It reverts back to thinking that you’re not. Which means calling a ‘cancelFullScreen’ request using a button will not work. My workaround for this was to attach a ‘requestFullScreen’ event prior to my ‘cancelFullScreen’ event on my button function. May not be elegant, but it works.

    3. Further along the same lines having navigated away from the original fullscreen state I created a JavaScript function detecting an ESC being pressed which reverts properly to the previous non-fullscreen state.

    If I’m mistaken, then please let me know and thanks for the hard work Mr. Dyer.

  31. Om Prakash says:

    It’s not working in IE browser….

  32. Anh.Nguyen says:

    Hi All,

    That full screen is cool, but i want full screen for attr body not attr (div).

    When i load complete page then full screen page, please help me!

  33. Anh.Nguyen says:

    Hi All,

    I want onload then fullscreen firefox, Can you help me its.

  34. […] (11/15/2011):来自 IEBlog的Ted Johnson说IE10将不会支持全屏API (12/05/2011: […]

  35. supernova says:

    Is it possible to request fullscreen to load an external page?

  36. Ala says:


    the API is great but i need add extra JS code when the user exit the full screen by press at ESC, ino your code i should insert it here

    fsElement.addEventListener(fullScreenApi.fullScreenEventName, function() {
    if (fullScreenApi.isFullScreen()) {
    fsStatus.innerHTML = ‘Whoa, you went fullscreen’;
    } else {
    fsStatus.innerHTML = ‘Back to normal’;
    //extra JS code

    }, true);

    its works fine at chrome but not at FF, hope can help me if i miss something

    thanks again

  37. Cristian Daniel says:

    Hey Guys. i am trying to implement the API. but not Success. i am quite new to JS. here what i am doing.
    copying the code into JS file working very well.

    when the DOM is ready i am implementing this code.

    try{switchToFULLScreen();}catch(E){alert(E);}//not exception is show…

    function switchToFULLScreen()
    var element = document.getElementById(‘rs2010’);//the element is visible… exist..
    alert(fullScreenApi.isFullScreen());//returning false;
    alert(fullScreenApi.supportsFullScreen);//return true;
    alert(fullScreenApi.isFullScreen());//returning false;
    i am using Google Chrome. 18.0 any help is very appreciate. please any suggest to my code or throught this page. God Bless.

  38. Cristian Daniel Ortiz says:

    Hey Guys. Is Working now. but i have a question… i need to resize the div when the fullscreen is toggling. the following code i am using.
    function switchToFULLScreen()
    var element = document.getElementById(‘outerdiv’);
    function switchToNormalScreen()
    var element = document.getElementById(‘outerdiv’);
    $(‘.big_center’).css(‘height’,’446.9%’); }
    Is Working well. but when i am doing manually. but i want to detect the F11 pressing to resize my div that’s is possible or not. thanks a lot.

  39. […] Native Fullscreen Javascript API […]

  40. siorpaesas says:

    In Chrome it works fine. But it always leaves full screen mode in FF once you click on another link. Looks like the script does not recognize the current status of full screen mode enabled.

  41. […] found John Dyer’s Native Fullscreen JavaScript API the other day, and I thought it was pretty […]

  42. This is fun. I tried it on my blog, and actually turned it into a WordPress plugin that I just released. Here it is, if you want to have a look :

  43. […] A proper fullscreen API (first proposed by Mozilla and later released as a W3C proposal) has been implemented by Webkit […]

  44. […] John Dyer’s Code sitesinden alınmıştır. Follow @P_Buyukarslan Tweet Jquery’de rel=”external” […]

  45. Alex says:

    Hi! This works great, thanks. I’ve used the code from the simple demo but I can’t figure out how to create a toggle function which would turn fullscreen on and off when a button is clicked. The button would be always visible on the screen and only change appearance via class name toggled by the same function.

    If anyone would be so kind to modify the code appropriately, that would be fab!

    var fsButton = document.getElementById(‘fsbutton’),
    fsElement = document.getElementById(‘specialstuff’),
    fsStatus = document.getElementById(‘fsstatus’);

    if (window.fullScreenApi.supportsFullScreen) {
    fsStatus.innerHTML = ‘YES: Your browser supports FullScreen’;
    fsStatus.className = ‘fullScreenSupported’;

    // handle button click
    fsButton.addEventListener(‘click’, function() {
    }, true);

    fsElement.addEventListener(fullScreenApi.fullScreenEventName, function() {
    if (fullScreenApi.isFullScreen()) {
    fsStatus.innerHTML = ‘Whoa, you went fullscreen’;
    } else {
    fsStatus.innerHTML = ‘Back to normal’;
    }, true);

    } else {
    fsStatus.innerHTML = ‘SORRY: Your browser does not support FullScreen’;

  46. Andrea says:

    Why it reload my website when entering in fullscreen mode?

  47. […] HTML5, folosind Flash ca variantă de rezervă. Ultimele versiuni de browsere implementează și Fullscreen API, astfel că un videoclip, de exemplu, poate fi urmărit pe ecranul întreg fără a mai fi nevoie […]

  48. Kristina says:

    Do you know why the fullscreen API would generate a black background in Safari, when there is no black background set?

  49. Truong Hua says:

    Thank for sharing, too interesting topic.
    There is an improvement for this that work with Internet Explorer

  50. […] Browser vendors are well aware of the potential security issues with fullscreen. For example, a malicious site could show a full screen Windows or Mac login window and steal a password. That’s why they are disabling keyboard support by default and only enabling by explicitly asking. — John Dyer […]

  51. lorenzo says:

    This works great, thank you!

    Only concern: as someone already pointed out browsers deactivate full screen mode when navigating out of the page. Safari is the only browser that (on my Macbook) keep fullscreen mode.

    Is there a way, with javascript, to keep fullscreen? like setting a variable that tells to the new loaded page to switch to full screen if the var == true?

  52. Hi there,
    great piece of code thanks for sharing!

    Problem is in FF 17.01 it throws an error on line 50 whether I implement it using straight js or use the jquery plugin:
    TypeError: el[(this.prefix + “RequestFullScreen”)] is not a function
    [Break On This Error]

    …(this.prefix === ”) ? el.requestFullScreen() : el[this.prefix + ‘RequestFullScr…

    This is how I am calling it, from within the click handler of a button:
    var fsElement = $(“body”);
    if (window.fullScreenApi.supportsFullScreen) {
    alert(‘YES: Your browser supports FullScreen’);


    fsElement.addEventListener(fullScreenApi.fullScreenEventName, function() {
    if (fullScreenApi.isFullScreen()) {
    alert(“in full screen”);
    } else {
    alert(“back to normal”);
    }, true);

    } else {
    alert(“not supported”);

    Any thoughts or ideas welcome…



  53. Tom says:

    hi John,

    I have finded a bug, I have modifed your demo, add ” in “”. After that, 1) open the page use chrome. 2)click the button “Go Fullscreen” 3)type number key(like “2”) in the “text” box -> the “text” box show nothing.
    All the number key and “e, a, d” and so on do not work in the input[type=”text”] when it use Native_FullScreen.js in chrome. Could you please help me to resolve it?


  54. […] Native Fullscreen JavaScript API plus jQuery plugin | John Dyer’s Code. […]

  55. Thank you for these great instructions!

  56. […] Native Fullscreen JavaScript API (plus jQuery plugin) | John … – To detect fullscreen support, … All the number key and “e, a, d” and so on do not work in the input[type="text"] when it use Native_FullScreen.js in chrome. Could you please help me to resolve it? Thanks. Reply. Native Fullscreen JavaScript API plus jQuery plugin … […]

  57. ugg boots says:

    2011Der Polizeichef einer kleinen Stadt südlich Texas wurde währenwe d einer Verkehrskontrolle am Sams2 erschossen, sagte ein County Sheriff!we

  58. chris lee says:

    Thank you for these great instructions! I was not sure what is native full screen looks like

  59. Hi there just wanted to give you a quick heads up. The text in your content seem to bbe running off the screen in Ie.
    I’m not sure if this is a formatting issue or something to do with browser compatibility but I thought I’d post
    to let yyou know. Thee layout look greeat though! Hope you get
    the problem resolved soon. Many thanks

    Feel frtee to visit mmy hpmepage – servizi fotografici milano

  60. domain says:

    Good day! I could have sworn I’ve been to this website before but after checking through
    some of the post I realized it’s new to me.
    Anyways, I’m definitely glad I found it and
    I’ll be book-marking and checking back often!

  61. Fabulous, what a webpage it is! This website presents useful facts to us, keep
    it up.

  62. Jay says:

    Excellent content you post here! You can earn some extra $$ from your page,
    don’t miss this opportunity, for more info just type in google – omgerido monetize website

  63. Whaat a waste of an existence and pitifully miserable.
    When we listrn to great music during a fitness routine, we feel more inclined to intensify our performance.
    Choose to spend your time witth positive people tjat can inspire yyou
    to keep following your targets.

    Look into my weeb page –

  64. It is combined with a tight lacing around the corset –
    – that is long enough to grid thhe whoile posture. Thin summer dresses with a
    broad belt arouind the waist are especially beautiful and girl-like.
    Looking your attractivebest even when you are in the house is similarly important.

  65. ElvinFyanszu says:

    I noticed your site’s ranking in google’s search results is very low.
    You are loosing a lot of traffic. You need high PageRank backlinks to rank in top10.
    I know – buying them is too expensive. It’s better to own them.
    I know how to do that, simply google it:
    Polswor’s Backlinks Source

  66. […] Native Fullscreen JavaScript API […]

  67. こんばんわ、アフィリエイター山本謙吾です。「順調にアフィリエイトで稼ぐ人」と「アフィリエイトで稼ぐことができない人」勝敗を分けるのは、様々なアフィリエイトツールを適正に用いているのか否か、といった部分に潜んでいるのです。友達「単独でネットで稼ぐのってどう?」と質問されますが、それに対しては山本謙吾「難しくしないやり方を会得すれば難しい事ではない」と伝えています。手書きでの宛名書きであったり食品パック・雑貨の検品など、頭を使わない単純作業の副業の場合は、子どもの側にいながら話しながらできる、TVを見つつ取り組めることから、専業主婦に注目されていると、山本謙吾はよく聞きます。もはやよく知られた私、山本謙吾もやっているアフィリエイト。ネット環境利用して稼ぐ案の山本お勧め具体的な一つとして、とにかくネットショップのように売れない商品を抱える不安要素もなく、気楽な気分で手を付けられるため、多くの人に支持されています。世の中には電話カウンセリングとして、心配事や悩み事、文句を聞いて相談を受けることで、月毎20万円を稼ぐといった主婦なども存在しております。話を伺うと副業を行い出して6年で、1日の平均が4~5時間で、この程度お金を得ているそうです。ネットで行う副業は1種類ではありません。いろいろな手法を駆使して、家にいながらにして利益を稼ぐことができ得るのです。好きなことに挑戦してみるのがよいかもしれません。山本謙吾も最初はそんな感じでした。概ねインターネットビジネスでしたら、勤務先の仕事に迷惑が掛からない状態で、サラリーマンが適度に副業するということにピッタリなビジネスラインが、何かと存在していると山本謙吾は思います。ミステリーショッパーについては、モニターとして様々な店舗に足を運び、接客態度などを調査するといった役割をするお仕事。すなわち、覆面調査員のことですね。主婦やOLたちの内で夢中になる人が、急増している副業と山本も聞いたことがあります。。時々見かけるアンケートモニターというのは用意されたアンケートに答えるだけで完了なので、都合の良い時間にネットで、誰でも問題なく行える山本謙吾的人気の副業です。2つ以上のサイトに登録しておくことで、さらなる報酬が得られます。大概個人での輸入ビジネスやまたネットオークションサイトを用いて稼ぐということは、言うならば通常の商売と同じようなビジネスジャンルとして捉えられると存じますが、れっきとしたネットビジネスの一つだと山本謙吾は考えます。たいていの場合、ネット輸入ビジネスと見比べて、ネットオークションを駆使して、マネーを稼ぐ方が、一段と容易で、かつ即金性をみても望めるので、未経験者を対象に是非利用して欲しいおすすめのネットビジネスであります。ビギナーがネットで稼ぐのであれば、いわゆるポイントサイトはマストです。単に紹介のみでも、収入を稼ぐことが出来てしまいます。手軽なポイントサイトは、ニックネーム的にお小遣い稼ぎサイトと言われています。山本謙吾がおすすめできる副業のファクターというのは、空いた時間を能率的に利用することが可能なこと、始めにかかるお金が少なくてOKであること、且つ言うまでもありませんが、収益がキッチリ稼げるということが絶対条件です。家計のやり繰りが上手な経験豊富な主婦の方がヒミツとしております、容易に良い収入を手にすることが出来ます最新の副業案件を多数山本謙吾がご紹介していきます。絶対にあなたにとって都合の良い仕事がスグサマ探し出すことができるはずです。一概に「副業」と言えど、そのタイプに関しましては多様であります。さしあたって「いったい何をしたらよいか皆目検討もつかない」といった未経験者は、まずもってランキング上位にインしている副業をやってみるといいかもしれません。山本謙吾もアドバイス致します!!

    Here is my site – 今後のアフィリエイター業界を山本謙吾が考える

  68. Chelsea says:

    Keep this going please, gret job!

  69. Your danger of reduced back pain during pregnancy increases if
    you have had back aches prior to becoming pregnant
    or throughout a previous pregnancy.

Hi, I'm John Dyer. In my day job, I build websites and create online seminary software for a seminary in Dallas. I also like to release open source tools including a pretty popular HTML5 video player and build tools that help people find best bible commentaries and do bible study. And just for fun, I also wrote a book on the theology of technology and media.

Fork me on GitHub

Social Widgets powered by