Look at this nasty code for HTML5 fullscreen usage. I thought we had moved past the day and age of needing to write proprietary/browser-specific code to get things to work? I'm very dissapointed in this implementation.
The browser-specific prefixes are there to say "this is still experimental, use at your own risk." Once the standard is solidified, the prefixes are unnecessary unless one is targetting older browsers prior to standardization.
This website uses cookies to improve your experience. More InfoAccept
Privacy policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
This site uses one temporary cookie, Spam Destroyer, which is necessary to help prevent spammers from submitting comments. This cookie is deleted automatically after an hour.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
+Michael Safyan thanks for the clarification!
The browser-specific prefixes are there to say "this is still experimental, use at your own risk." Once the standard is solidified, the prefixes are unnecessary unless one is targetting older browsers prior to standardization.