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