1<!DOCTYPE html> 2<html lang="en"> 3 4<head> 5 <title>HTML5test - How well does your browser support HTML5?</title> 6 <meta charset="UTF-8"> 7 <meta name="apple-mobile-web-app-capable" content="yes"> 8 <meta name="apple-mobile-web-app-status-bar-style" content="black"> 9 <meta name="viewport" content="width=device-width, initial-scale=1.0"> 10 <link rel="stylesheet" href="/css/main.css" type="text/css"> 11 <meta name="application-name" content="HTML5test"> 12 <link rel="apple-touch-icon" sizes="57x57" href="/images/icons/apple-touch-icon-57x57.png"> 13 <link rel="apple-touch-icon" sizes="114x114" href="/images/icons/apple-touch-icon-114x114.png"> 14 <link rel="apple-touch-icon" sizes="72x72" href="/images/icons/apple-touch-icon-72x72.png"> 15 <link rel="apple-touch-icon" sizes="144x144" href="/images/icons/apple-touch-icon-144x144.png"> 16 <link rel="apple-touch-icon" sizes="60x60" href="/images/icons/apple-touch-icon-60x60.png"> 17 <link rel="apple-touch-icon" sizes="120x120" href="/images/icons/apple-touch-icon-120x120.png"> 18 <link rel="apple-touch-icon" sizes="76x76" href="/images/icons/apple-touch-icon-76x76.png"> 19 <link rel="apple-touch-icon" sizes="152x152" href="/images/icons/apple-touch-icon-152x152.png"> 20 <link rel="icon" type="image/png" href="/images/icons/favicon-16x16.png" sizes="16x16"> 21 <link rel="icon" type="image/png" href="/images/icons/favicon-32x32.png" sizes="32x32"> 22 <link rel="icon" type="image/png" href="/images/icons/favicon-96x96.png" sizes="96x96"> 23 <link rel="icon" type="image/png" href="/images/icons/favicon-160x160.png" sizes="160x160"> 24 <link rel="icon" type="image/png" href="/images/icons/favicon-196x196.png" sizes="196x196"> 25 <meta name="msapplication-TileColor" content="#0092bf"> 26 <meta name="msapplication-TileImage" content="/images/icons/mstile-144x144.png"> 27</head> 28 29<body> 30 <div class='header'> 31 <h1><span>HTML<strong>5</strong>test</span> <em>how well does your browser support HTML5?</em></h1> 32 <div class='navigation'> 33 <ul class='left'> 34 <li><a href='/'>Your browser</a></li> 35 <li><a href='/results/desktop.html'>Other<span> browser</span>s</a></li> 36 <li><a href='/compare/browser/'>Compare</a></li> 37 </ul> 38 <ul class='right'> 39 <li class='selected'><a href='/about.html'>About<span> the test</span></a></li> 40 </ul> 41 </div> 42 </div> 43 44 <div class='page'> 45 <div class='column'> 46 <div class='paper hasNavigation'> 47 <ul class='navigation'> 48 <li class='selected'><a href='/about.html'>Frequently asked questions</a></li> 49 </ul> 50 51 <div> 52 <h2>Specifications</h2> 53 54 <h3>Why do you include specifications that are not part of HTML5?</h3> 55 <div class='text'> 56 <p> 57 HTML5 means different things to different people. You could argue that HTML5 only includes features that are 58 defined in the W3C HTML5 specification. Or you could argue that it includes every specification, draft or 59 experimental feature that is added to browsers in the last couple of years. We decided to take the middle 60 ground and split the test into three parts: the official HTML5 specification, specifications that are related 61 to HTML5 and some experimental new features that are extensions of HTML5. 62 </p> 63 <p> 64 Many of the related specifications were at one time part of HTML5. During the development of the specification 65 they were moved to separate specifications. 66 </p> 67 </div> 68 69 <h3>But WebGL isn't even a W3C specification!</h3> 70 <div class='text'> 71 The W3C isn't the only organization that creates open specifications for the web. The WebGL specification is 72 published by Kronos, the same group that is also responsible for OpenGL. WebGL is related to HTML5 though and 73 listed as one of the HTML5 technologies on the W3C HTML5 logo page. The W3C HTML5 specification allows the 74 canvas element to be extended by new drawing methods and WebGL is one of them. 75 </div> 76 77 <h3>Why do you test for Web SQL?</h3> 78 <div class='text'> 79 The Web SQL specification has been deprecated and replaced by the IndexedDB specification. It is however 80 still commonly used on mobile phones and at least three vendors have shipped desktop browsers supporting Web SQL. We've decided to include 81 this specification, but make it a special case. Web SQL is worth 5 points, but only if IndexedDB is not supported. 82 IndexedDB is worth 10 points. If a browser supports both, only 10 points are awarded. This way browsers 83 that only included IndexedDB are not penalized, but browsers that only support Web SQL do get some points. 84 </div> 85 86 <hr> 87 88 89 <h2>Scoring</h2> 90 91 <h3>What is the maximum number of points you can score?</h3> 92 <div class='text'> 93 If a browser passes all tests it would receive the maximum score of 555. Previous 94 versions of the HTML5test had less tests and therefore also a lower maximum score, such as 160, 300, 450, 475 and 500 points. 95 Previous versions of this test also awarded bonus points for some features, but as of version 5, we 96 no longer do. 97 </div> 98 99 <h3>The scoring seems arbitrary, who decides how many points are awarded?</h3> 100 <div class='text'> 101 We decided to award points for each feature depending on how important that feature is for web developers 102 and how difficult it is to implement that feature. A small and simple feature would be worth less points than a 103 large and complicated feature. We think this is the most honest way to grade browsers, because otherwise a browser 104 that only supports the small and simple features would score as high or higher than a browser that went the 105 extra mile and decided to tackle the big features. But in the end it is based on personal preference, 106 but I doubt there is a truly objective alternative. 107 </div> 108 109 <hr> 110 111 112 <h2>Reporting</h2> 113 114 <h3>Can my browser be included on the 'other browser' and 'compare' pages?</h3> 115 <div class='text'> 116 <p> 117 We would love to add new browsers, but not all browsers are eligible. First of all we only accept browsers that 118 are publicly available, either in beta form or a final release. We do not accept scores for internal development builds. 119 Secondly we only accept browsers that are available in English. We want to check browsers before including them and 120 unfortunately we do not speak Chinese, Japanese, Korean or Russian. And finally we only accept browsers which have a 121 unique score. There are many browsers that are forks or modified versions of Chromium or Firefox. Similarly there 122 are many browser that embed Internet Explorer or Webkit as provided by the operating system. These browser 123 do not qualify. For comparisons, simply choose the original browser on which the browser was based instead. 124 </p> 125 <p> 126 We retain the right to make exceptions to any of the rules above and to remove or refuse any browser we deem 127 necessary. 128 </p> 129 </div> 130 131 <h3>What happens when a browser cheats?</h3> 132 <div class='text'> 133 <p> 134 We cannot distinguish between a browser that supports a particular feature and a browser that lies about supporting 135 that feature. The only way to deal with these situations it to manually confirm the test results. And if a browser 136 is found to be overly confident about claiming support for certain features we can put that browser on a blacklist.
137 That means that that even though the browser claims to support a particular feature, we ignore what the browser says and do 138 not give any points. This is usually just a temporary problem and once the browser has been fixed we will remove 139 the new version from the blacklist. 140 </p> 141 <p> 142 Claiming to support a feature which isn't working is not just causing problems for the reliability of the 143 test results, but there are other real-world problems. For example if you claim to support WebGL, a website may decide 144 to serve WebGL content. If your browser does not support WebGL, the website may fail in an uncontrollable way. If you 145 correctly denied support for WebGL, the website may have served alternative content that would work in your browser. 146 If you claim to support features that you don't, you are breaking the web. 147 </p> 148 <p> 149 If we find that a browser is structurally lying about which features they support - deliberately or not - we will 150 usually give a warning to the developers of the browser and if the problem hasn't been fixed in the next version 151 we will remove the browser from the 'other browser' and 'compare' pages and/or give other penalties. In extreme 152 cases we may block the browser from showing test results and show a warning instead. 153 </p> 154 </div> 155 156 <hr> 157 158 <h2>Methods</h2> 159 160 <h3>Why are you using browser sniffing?</h3> 161 <div class='text'> 162 <p> 163 Unfortunately, in two very specific cases we are forced to use browser sniffing. The first case is <code>contentEditable</code> 164 which was not supported on many older mobile devices. Yet almost all mobile browsers claim to support <code>contentEditable</code>. 165 Fortunately modern mobile devices are starting to support <code>contentEditable</code>, but this left us with a problem. We 166 cannot reliably detect if a browser has proper support. The only way around this is to use a whitelist of 167 mobile browsers that do support this feature, otherwise you risk awarding points to mobile browsers that they 168 do not deserve. The second case is drag and drop, which is also not supported on mobile phones and tablets. </p> 169 <p> 170 Please open a new issue on <a href='https://github.com/niutech/html5test'>Github</a> when you believe a 171 browser should be included on the whitelist. 172 </p> 173 </div> 174 175 <hr> 176 177 <h2>Privacy</h2> 178 179 <h3>What kind of data is collected from visitors?</h3> 180 <div class='text'> 181 <p> 182 Each time you visit this website your score and test results are logged on our servers. 183 We also store the user agent of your browser which contains information about the browser, 184 operating system and device you are using. The collected information is solely used to 185 generated anonymized reports about HTML5 support in browsers and improve the quality of 186 our software. 187 </p> 188 <p> 189 We do not store cookies in your browser. 190 </p> 191 </div> 192 </div> 193 </div> 194 195 <div class='footer'> 196 <div> 197 <div class='copyright'> 198 <p> 199 © 2025 - Created by Niels Leenheer, modified by Jerzy GÅowacki.<br> 200 Please note that the HTML5 test is not affiliated with the W3C or the HTML5 working group.<br> 201 HTML5 Logo by <a href="http://www.w3.org/" target="_blank"><abbr title="World Wide Web Consortium">W3C</abbr></a>. 202 Browser detection by <a href="http://whichbrowser.net" target="_blank">WhichBrowser</a>. 203 CORS proxy by <a href="https://corsfix.com" target="_blank">Corsfix</a>. 204 </p> 205 </div> 206 </div> 207 </div> 208 </div> 209 </div> 210</body> 211 212</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.