forked from h5bp/html5please
-
Notifications
You must be signed in to change notification settings - Fork 0
/
index.html
2527 lines (2051 loc) · 138 KB
/
index.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
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!doctype html>
<html class="no-js" lang="en">
<head>
<meta charset="utf-8">
<meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible">
<title>HTML5 Please - Use the new and shiny responsibly</title>
<meta name="description" content="Look up HTML5, CSS3, etc features, know if they are ready for use, and if so find out how you should use them – with polyfills, fallbacks or as they are.">
<meta content="width=device-width, initial-scale=1.0" name="viewport">
<link rel="shortcut icon" href="favicon.ico" />
<link rel="apple-touch-icon-precomposed" sizes="114x114" href="apple-touch-icon-114x114-precomposed.png">
<link rel="apple-touch-icon-precomposed" sizes="72x72" href="apple-touch-icon-72x72-precomposed.png">
<link rel="apple-touch-icon-precomposed" href="apple-touch-icon-precomposed.png">
<link href="http://fonts.googleapis.com/css?family=Francois+One|Open+Sans:400italic,400,800" rel="stylesheet">
<link href="css/style.css" rel="stylesheet">
<script src="js/libs/modernizr-2.0.min.js"></script>
<script>if (location.host == 'h5bp.github.com') location.href = '//html5please.us/'</script>
</head>
<body id="gfs">
<header class="index">
<h1>HTML5 <img src="img/HTML5-logo.png" alt="HTML5 Logo"> Please</h1>
<h2>
<b>Use the new and shiny responsibly.</b>
<p>Look up HTML5, CSS3, etc features, know if they are ready for use, and if so find out how you should use them – with polyfills, fallbacks or as they are. <a href="#moredetails" id="clickmore">tell me more</a>
</p>
<div id="moredetails">
<p><a href="http://caniuse.com">When Can I Use</a> tells you the browser support story, while <a href="http://modernizr.com">Modernizr</a> gives you the power of feature detection. HTML5 Please helps you out with recommendations for <a href="https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-browser-Polyfills">polyfills</a> and implementation so you can decide if and how to put each of these features to use.</p>
<p>The recommendations below represent the collective knowledge of developers who have been deep in the HTML5 trenches. We hope they serve you well.</p>
<p>Read Divya's backstory <a href="http://nimbupani.com/html5please.html">about this site</a>.</p>
</div>
</h2>
<div>
<input id="livesearch" class="search" name="livesearch" placeholder="type to filter" type="search" value="" autofocus />
<a href="/" id="searchurl">link to this search ›</a>
<div class="explore-features">
<h2><b>Explore</b> features</h2>
<ul>
<li>supported by <a href="#gtie9">IE10+</a> <a href="#gtie8">IE9+</a> <a href="#gtie7">IE8+</a> <a href="#gtie6">IE7+</a> <a href="#noie">no IE</a> </li>
<li>not supported by <a href="#nomobile">mobile devices</a> <a href="#nooldmobile">older mobile devices</a></li>
<li>requiring <a href="#prefixes">prefixes</a><a href="#polyfill">polyfill</a><a href="#fallback">fallback</a></li>
<li>that you should <a href="#use">use</a> <a href="#caution">use with caution</a> <a href="#avoid">avoid</a></li>
<li>that are <a href="#css">css</a> <a href="#html">html</a><a href="#api">api</a><a href="#js">js</a></li>
<li> <a href="#showall">all features</a></li>
</ul>
</div>
</div>
</header>
<div id="main" role="main">
<section class="features list">
<article class="fallback">
<header>
<h2 class="name" id="animations">animations </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Animations are now supported in the latest versions of almost all browsers. In order to provide support for slightly older browsers, either use animations only to provide non-essential aesthetic enhancements or use feature detection to provide an alternative experience for browsers that do not support this feature.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/animations">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/animations.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback</footer>
</article>
<article class="polyfill">
<header>
<h2 class="name" id="<audio>"><audio> </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p>As is the case with video, you need to provide your audio file in multiple formats for these to work, namely in <a href="http://www.scirra.com/blog/44/on-html5-audio-formats-aac-and-ogg">Ogg Vorbis and AAC</a>. jPlayer has a jQuery dependency. Sound Manager has an extensive API for further customization. <a href="http://mediaelementjs.com/">mediaelement.js</a> offers the HTML5 media element API through Flash in the fallback case and offers uniform styling across browsers and to the Flash widget.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://mediaelementjs.com/">mediaelement.js</a>, <a href="https://github.com/happyworm/jPlayer">jPlayer</a>, <a href="http://www.schillmania.com/projects/soundmanager2/">Sound Manager 2</a></p></div>
<p class="links">
<a href="http://caniuse.com/audio">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/audio.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill</footer>
</article>
<article class="gtie8 fallback">
<header>
<h2 class="name" id="background-image options">background-image options </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>CSS3 <code>background-image</code> options include <code>background-clip</code>, <code>background-origin</code> and <code>background-size</code>. Just ensure that your background image does not make it unreadable on IE8- where these properties are not supported. Also, when using <code>background-image</code> make sure you have a fallback color in case the image fails to load. </p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/background-image">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/background-image.md">Edit this info</a>
</p>
</div>
<footer class="tags">gtie8 fallback</footer>
</article>
<article class="fallback prefixes">
<header>
<h2 class="name" id="border-image">border-image </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Make sure to use all the right prefixes (<code>-o-</code>, <code>-webkit-</code>, <code>-ms-</code>, <code>-moz-</code>). Additionally, <a href="http://border-image.com/">border-image.com</a> may help. You should let this fall back to either a normal solid border or no border at all, depending on whether a border is essential for readability. We recommend that you avoid polyfills.</p>
<p>There were some syntax changes (requiring the <code>fill</code> keywords) that may catch you off-guard; <a href="http://dbaron.org/log/20120612-border-image">David Baron's border-image post</a> describes the best course of action.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/border-image">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/border-image.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback prefixes</footer>
</article>
<article class="">
<header>
<h2 class="name" id="border-radius">border-radius </h2>
<h3 class="status use">use <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p><code>border-radius</code> can be safely used without a prefix for all modern browsers, and gracefully renders rectangles when not supported. However, note that applying this to a large area and on many elements <a href="http://perfectionkills.com/profiling-css-for-fun-and-profit-optimization-notes/">might cause significant performance</a> impact when scrolling or when the window is redrawn. </p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/border-radius">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/border-radius.md">Edit this info</a>
</p>
</div>
<footer class="tags"></footer>
</article>
<article class="none">
<header>
<h2 class="name" id="box-reflection">box-reflection </h2>
<h3 class="status avoid">avoid <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>The <code>box-reflect</code> property has never been part of any CSS specification. Certain presentations that are possible with <code>-webkit-box-reflect</code> will be possible using CSS Filters. You should avoid using WebKit-only box reflections.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://www.webkit.org/blog/182/css-reflections/">
Learn more
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/box-reflection.md">Edit this info</a>
</p>
</div>
<footer class="tags">none</footer>
</article>
<article class="prefixes">
<header>
<h2 class="name" id="box-shadow">box-shadow </h2>
<h3 class="status caution">caution <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p><code>box-shadow</code> is safe to use most of the time, except when you are applying it on a large area as that may cause significant performance impact when interacting with the page (on scroll and hovers, but also transitions and animations). </p>
<p>Polyfills are unnecessary for box-shadow. They are too costly and slow down page load. Users without a modern browser will not see a shadow, but aren't checking your site in multiple browsers anyhow.</p>
<p>Box shadows can also be applied safely without prefixes. </p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/box-shadow">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/box-shadow.md">Edit this info</a>
</p>
</div>
<footer class="tags">prefixes</footer>
</article>
<article class="fallback prefixes gtie7 border-box">
<header>
<h2 class="name" id="box-sizing">box-sizing </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Supported in Chrome, IE8+, Opera, Safari 5.1+. The <a href="http://paulirish.com/2012/box-sizing-border-box-ftw/">recommended pattern</a> is <code>box-sizing : border-box;</code>, preceded by the fallbacks <code>-webkit-box-sizing: border-box;</code> for old IOS<=4 and Android<=3, and <code>-moz-box-sizing: border-box;</code> for Firefox. You can apply it to all (<code>*</code>) elements if you like.</p>
<p>IE8 does not support <code>box-sizing: border-box;</code> with <code>min-width</code>/<code>max-width</code> and <code>min-height</code>/<code>max-height</code>. For IE6/7 you can optionally use the <a href="https://github.com/Schepp/box-sizing-polyfill">box-sizing polyfill</a> to provide this feature in IE 6/7 (you could scope the adjustments using <a href="http://paulirish.com/2008/conditional-stylesheets-vs-css-hacks-answer-neither/">IE conditionals</a> or Modernizr's <a href="http://www.modernizr.com/download/#-cssclasses-addtest-css_boxsizing"><code>no-box-sizing</code></a>).</p>
<p>Besides the prefix, there were box sizing issues in Gecko/Firefox, see <a href="https://developer.mozilla.org/En/CSS/Box-sizing#Notes">notes at MDN</a>. For versions of Firefox before 17 min-height/max-height does not work.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/box-sizing">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/box-sizing.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback prefixes gtie7 border-box</footer>
</article>
<article class="fallback">
<header>
<h2 class="name" id="calc()">calc() </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>All the modern browsers except Android's native browser support <code>calc()</code> which makes it easier to adopt. But do note that it can have a big impact on the layout and the consequent breaking of your design on unsupported browsers. </p>
<p>You should use it with a fallback declaration, so it doesn't break browsers which don't support it.</p>
<pre><code>width: 500px; /** older browsers **/
width: -webkit-calc(50% - 20px); /** Safari 6, Chrome 19-25 **/
width: -moz-calc(50% - 20px); /** FF 4-15 **/
width: calc(50% - 20px); /** FF 16+, IE 9+, Opera 15, Chrome 26+, Safari 7 and future other browsers **/
</code></pre>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/calc">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/calc.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback</footer>
</article>
<article class="gtie8 polyfill">
<header>
<h2 class="name" id="<canvas>"><canvas> </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p><code>canvas</code> is definitely good to go for modern browsers. If you want to support Internet Explorer 8 and below, ExplorerCanvas and FlashCanvas can be helpful in providing support for most <code>canvas</code> features. However, due to the complex nature of native <code>canvas</code> implementations, developers should be aware that the polyfills for <code>canvas</code> are not simple drop-in solutions in some cases.</p>
<p>For example, both <a href="https://groups.google.com/forum/?fromgroups#!searchin/google-excanvas/drawImage">ExplorerCanvas</a> and <a href="https://groups.google.com/forum/?fromgroups#!searchin/flashcanvas/drawImage">FlashCanvas</a> may have difficulties handling the commonly used <code>drawImage</code> method. FlashCanvas cannot be passed the bitmap data from a DOM-based <code>Image</code> object, and therefore has to re-request the asset in the Flash Player causing undesired latency and flickering. Developers should be careful when handling image data and ensure thorough testing due to the unreliability and technical limitations of these features in the polyfills.</p>
<p>That isn't to say <code>canvas</code> shouldn't be used if cross-browser compatibility is a concern. Existing polyfills are more than capable of rendering simpler bitmaps such as <a href="http://www.jqplot.com/deploy/dist/examples/kcp_pyramid2.html">charts/graphs</a>, <a href="http://thejit.org/static/v20/Jit/Examples/Sunburst/example2.html">visualizations</a>, and even <a href="http://flashcanvas.net/examples/www.chiptune.com/starfield/starfield.html">starfields</a>! For these uses and many more, <code>canvas</code> is highly encouraged.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://flashcanvas.net/">FlashCanvas</a>, <a href="http://code.google.com/p/explorercanvas/">ExplorerCanvas</a></p></div>
<p class="links">
<a href="http://caniuse.com/canvas">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/canvas.md">Edit this info</a>
</p>
</div>
<footer class="tags">gtie8 polyfill</footer>
</article>
<article class="polyfill noie nooldmobile">
<header>
<h2 class="name" id="classList">classList </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>classList is a relatively new feature which may not be available in older browsers and Internet Explorer <= 9. While this is not a concern if you are using a library like jQuery to modify class names, make sure you use the polyfill when using classList directly.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/eligrey/classList.js">classlist.js</a></p></div>
<p class="links">
<a href="http://caniuse.com/classlist">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/classlist.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill noie nooldmobile</footer>
</article>
<article class="polyfill">
<header>
<h2 class="name" id="CORS">CORS </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p>CORS, or cross-origin resource sharing, enables a few things, but most notably cross-domain AJAX. All non-IE browsers have support for CORS. IE8 introduced <a href="http://msdn.microsoft.com/en-us/library/ie/cc288060(v=vs.85).aspx">XDomainRequest</a>, so really only IE7 needs help with cross-domain files. Consider the flXHR polyfill or you can fall back to using a <a href="http://benalman.com/projects/php-simple-proxy/">simple proxy</a>.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/flensed/flXHR">flXHR</a> (requires crossdomain.xml)</p></div>
<p class="links">
<a href="http://caniuse.com/cors">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/cors.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill</footer>
</article>
<article class="prefixes">
<header>
<h2 class="name" id="css filters">css filters </h2>
<h3 class="status caution">caution <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Filters are now supported by Safari 6+, Opera 15+, and Chrome 18+. But, given the lack of support in other browsers, consider waiting for other implementations before use.</p>
<p>If you can't wait, give <a href="https://github.com/Schepp/CSS-Filters-Polyfill">Polyfilter - a CSS Filters Polyfill</a> a spin which supports/translates to/emulates filters on Chrome 20+, Safari 6+, Firefox 4+, IE 6-9 (but not IE 10) on desktop and iOS 6+ Safari and Chrome, and Firefox 4+ on mobile.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/Schepp/CSS-Filters-Polyfill">Polyfilter - a CSS Filters Polyfill</a></p></div>
<p class="links">
<a href="http://css3clickchart.com/#filters">
Learn more
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/css-filters.md">Edit this info</a>
</p>
</div>
<footer class="tags">prefixes</footer>
</article>
<article class="fallback gtie8">
<header>
<h2 class="name" id="css3 colors">css3 colors </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>If you found yourself wanting to use <code>papayawhip</code> or <code>goldenrod</code> or <code>indianred</code> as your colors of choice, do feel free. You have to specify a fallback color for IE 8- users. Use the HSL(), HSLA() and RGBA() functions with more caution, as they may not be supported on older browsers.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/css3-colors">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/css3-colors.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback gtie8</footer>
</article>
<article class="polyfill gtie9 nomobile">
<header>
<h2 class="name" id="<datalist>"><datalist> </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p><a href="http://developers.whatwg.org/the-button-element.html#the-datalist-element"><code><datalist></code></a> enables autocomplete combo boxes. It can be polyfilled well with any of the scripts below, though they have <a href="https://github.com/h5bp/html5please/issues/18">varying levels</a> of support for the full feature. You can also use a <a href="http://adactio.com/journal/4272/">graceful fallback</a> if you choose not to polyfill.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://css-tricks.com/relevant-dropdowns-polyfill-for-datalist/">Relevant Dropdowns</a>, <a href="http://afarkas.github.com/webshim/demos/">Webshims</a>, <a href="http://miketaylr.com/code/datalist.html">jQuery Datalist Plugin</a></p></div>
<p class="links">
<a href="http://caniuse.com/datalist">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/datalist.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill gtie9 nomobile</footer>
</article>
<article class="fallback noie nooldmobile">
<header>
<h2 class="name" id="dataset">dataset </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p><code>elem.dataset</code> is unsupported in Internet Explorer <= 10 and older mobile browsers. Using data-* attributes will be totally fine in all browsers, but instead of using <code>elem.dataset.foo</code> just use <code>elem.getAttribute('data-foo')</code>. A polyfill is availble if you want terser syntax.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://eligrey.com/blog/post/html-5-dataset-support">HTML5 dataset support</a></p></div>
<p class="links">
<a href="http://caniuse.com/dataset">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/dataset.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback noie nooldmobile</footer>
</article>
<article class="polyfill">
<header>
<h2 class="name" id="<details>"><details> </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p>Use the details element if you intend to show a summary which, when clicked, reveals detailed information. Without any fallback, non-supporting browsers will fall back to displaying the element in the opened state.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://mathiasbynens.be/notes/html5-details-jquery">Details</a>, <a href="http://akral.bitbucket.org/details-tag">jquery-details</a></p></div>
<p class="links">
<a href="http://caniuse.com/details">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/details.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill</footer>
</article>
<article class="polyfill">
<header>
<h2 class="name" id="DOM">DOM </h2>
<h3 class="status caution">caution <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>A large subset of <a href="http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html">the DOM</a> can currently be correctly shimmed. However the current shims are not fully tested and are missing some features.</p>
<p>Experimentally use with caution until the shim implementations have matured.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/termi/ES5-DOM-SHIM">ES5-DOM-shim</a>, <a href="https://github.com/Raynos/DOM-shim">DOM-shim</a></p></div>
<p class="links">
<a href="http://caniuse.com/dom">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/dom.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill</footer>
</article>
<article class="polyfill nomobile">
<header>
<h2 class="name" id="drag n drop">drag n drop </h2>
<h3 class="status caution">caution <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>Drag and Drop has been standardized in HTML5 based on Internet Explorer's original implementation. Therefore, it already has wide support, but many feel frustrated when using the API. You may want to use jQuery UI Draggable (or another JavaScript library) to handle this for you. Meanwhile the proposed <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#the-dropzone-attribute">[dropzone]</a> attribute will improve the situation as it gains browser support.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/MrSwitch/dropfile">dropfile</a>, <a href="https://github.com/eligrey/FileSaver.js">fileSaver</a>, <a href="https://github.com/vjeux/jDataView">jDataView</a></p></div>
<p class="links">
<a href="http://caniuse.com/dragndrop">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/dragndrop.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill nomobile</footer>
</article>
<article class="fallback gtie8 nooldmobile es5">
<header>
<h2 class="name" id="ECMAScript 5">ECMAScript 5 </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind js">js</h4>
</header>
<div class="more">
<div class="recco">
<p>ECMAScript version 5 covers a large number of feature additions to what we normally call JavaScript.
Excluding IE8, <a href="http://kangax.github.com/es5-compat-table/">most of ES5 is supported in browsers</a>.
As it introduces no new syntax, it's possible to polyfill fairly well.
The below polyfills tackle most uses of these features, but <a href="https://gist.github.com/1664895">there is an unshimmable subset of ES5</a>.
Also note that some shims are known to have <a href="https://gist.github.com/1120592">edgecase compliance bugs</a>.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/kriskowal/es5-shim/">es5-shim</a>, <a href="http://augmentjs.com/">augment.js</a></p></div>
<p class="links">
<a href="http://caniuse.com/ec">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/ec.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback gtie8 nooldmobile es5</footer>
</article>
<article class="es6">
<header>
<h2 class="name" id="ECMAScript 6">ECMAScript 6 </h2>
<h3 class="status avoid">avoid <i></i> </h3>
<h4 class="kind js">js</h4>
</header>
<div class="more">
<div class="recco">
<p>ECMAScript version 6 is the upcoming version of JavaScript that brings new features and heavy syntax changes. Currently only Chrome(17+) and Firefox support a highly experimental subset of ES6 features. </p>
<p>There is a <a href="https://github.com/paulmillr/es6-shim">ES6-shim</a> that attempts to shim a subset of ES6 however this subset is quite small, see the <a href="https://gist.github.com/1665192">ES6 shim status</a> for more details</p>
<p>Since ES6 brings new syntax to the language the best way to handle cross browser compliance is using a ES6 to ES3 compiler. However although there are a few projects in progress, none are ready to use.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://www.2ality.com/2013/07/es6-modules.html">
Learn more
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/es6.md">Edit this info</a>
</p>
</div>
<footer class="tags">es6</footer>
</article>
<article class="fallback">
<header>
<h2 class="name" id="EventSource">EventSource </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p><a href="http://html5doctor.com/server-sent-events/">Server-Sent Events</a> are real-time events emitted by the server and received by the browser. EventSource.js provides a base fallback and is not dependent on jQuery.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/remy/polyfills/blob/master/EventSource.js">EventSource.js</a>, <a href="https://github.com/rwldrn/jquery.eventsource">jQuery.eventsource</a></p></div>
<p class="links">
<a href="http://caniuse.com/Eventsource">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/Eventsource.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback</footer>
</article>
<article class="none">
<header>
<h2 class="name" id="exclusions">exclusions </h2>
<h3 class="status avoid">avoid <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Exclusions are new and exciting, but very much in flux. Active development to get an implementation out is on-going, but again, please avoid using this until there are stable implementations in the wild.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://css3clickchart.com/#exclusions">
Learn more
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/exclusions.md">Edit this info</a>
</p>
</div>
<footer class="tags">none</footer>
</article>
<article class="prefixes polyfill">
<header>
<h2 class="name" id="File API">File API </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>Using the File API added to the DOM in HTML5, it's now possible for web content to ask the user to select local files.</p>
<p>FileReader pairs very well with Drag n Drop to allow for drag 'n drop file uploads, and if neither of those features are present, the fallback of providing an <code><input type=file></code> is rather easy.
Supported in Chrome, Firefox, Opera. Safari is currently missing FileReader support.</p>
<ul>
<li><a href="https://github.com/Jahdrien/FileReader">FileReader</a> provides useful fallback, based on Flash, jQuery and jQuery UI. Doesn't support readAsBinaryFile.</li>
<li><a href="https://github.com/moxiecode/moxie">moxie</a> extracted from Plupload, actively maintained as of 6/3/13.</li>
</ul>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/Jahdrien/FileReader">FileReader</a>, <a href="https://github.com/moxiecode/moxie">moxie</a></p></div>
<p class="links">
<a href="http://caniuse.com/fileapi">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/fileapi.md">Edit this info</a>
</p>
</div>
<footer class="tags">prefixes polyfill</footer>
</article>
<article class="prefixes polyfill">
<header>
<h2 class="name" id="FileSystem & FileWriter API">FileSystem & FileWriter API </h2>
<h3 class="status avoid">avoid <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>Filesystem API provides a method of reading and writing files to a sandboxed file system on the user's local file system.
Supported only by Chrome 18+ with webkit prefix. Check out <a href="http://caniuse.com/filesystem">http://caniuse.com/filesystem</a> for a better understanding of the support.</p>
<p><a href="https://github.com/ebidel/idb.filesystem.js">idb.filesystem.js</a> Implements a polyfill using IndexedDB as its underlying storage layer. Required support for IndexDB means that it works only in Firefox and Chrome.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/ebidel/idb.filesystem.js">idb.filesystem.js</a></p></div>
<p class="links">
<a href="http://caniuse.com/filesystem">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/filesystem.md">Edit this info</a>
</p>
</div>
<footer class="tags">prefixes polyfill</footer>
</article>
<article class="none flexible">
<header>
<h2 class="name" id="flexbox">flexbox </h2>
<h3 class="status use">use <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>The flexbox spec has changed significantly through three major revisions (Chris Coyier has a <a href="http://css-tricks.com/old-flexbox-and-new-flexbox/">post on how to tell which flexbox you're looking at</a>). <a href="http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/">Older versions of this spec</a> were implemented in Gecko and WebKit. (a tutorial covering that spec is <a href="http://www.html5rocks.com/en/tutorials/flexbox/quick/">on HTML5 Rocks</a>). The current version is now a W3C Candidate Recommendation and is considered stable. There are presently no robust polyfills for the current spec, however it's possible to <a href="http://css-tricks.com/using-flexbox/">mix old and new flexbox for maximum browser support</a>.</p>
<p>The spec is now implemented in Opera, Chrome, IE and Firefox. <a href="http://weblog.bocoup.com/dive-into-flexbox/">Dive into Flexbox</a> is a good overview of the spec from Bocoup, Opera has a great tutorial to learn from: <a href="http://dev.opera.com/articles/view/flexbox-basics/">Flexbox — fast track to layout nirvana?</a>. Additionally, the <a href="https://developer.mozilla.org/en-US/docs/CSS/Using_CSS_flexible_boxes">flexbox docs at MDN</a>, <a href="http://css-tricks.com/snippets/css/a-guide-to-flexbox/">A Complete Guide to Flexbox</a>, and <a href="http://philipwalton.github.io/solved-by-flexbox/">Solved by Flexbox</a> are good references alongside playgrounds like <a href="http://demo.agektmr.com/flexbox/">Flexbox Please!</a>, <a href="http://the-echoplex.net/flexyboxes/">Flexy Boxes</a>, and <a href="http://bennettfeely.com/flexplorer/">Flexplorer</a>.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/flexbox">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/flexbox.md">Edit this info</a>
</p>
</div>
<footer class="tags">none flexible</footer>
</article>
<article class="fallback">
<header>
<h2 class="name" id="@font-face">@font-face </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Use <a href="http://www.google.com/fonts">Google Fonts</a> for hundreds of free, open-source fonts optimized for the web. <a href="http://www.fontsquirrel.com/fontface/generator">Font Squirrel Generator</a> for fonts you have license for using as web fonts. <a href="http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax">Fontspring @font-face syntax</a> is also the most bullet-proof way of serving web fonts. You do not need polyfills - just fonts in several formats; WOFF is preferred, followed by TTF and then EOT. </p>
<p>Also, don't use solutions like sIFR or Cufon anymore, as they can cause accessibility and performance problems.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/fontface">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/fontface.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback</footer>
</article>
<article class="none">
<header>
<h2 class="name" id="font-feature-settings">font-feature-settings </h2>
<h3 class="status use">use <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>Internet Explorer 10, Firefox 4+ and Chrome 16 (Windows and Linux only) support low level control over font feature settings. What this means is other browsers merely will not render the flourishes you seek. Many features available through the property may be extracted to separate properties in the future, such as font-variant-ligatures. </p>
<p>More at <a href="http://www.typotheque.com/articles/opentype_features_in_web_browsers">OpenType features in web browsers</a></p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://blog.fontdeck.com/post/15777165734/opentype-1?503cde40">
Learn more
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/font-feature-settings.md">Edit this info</a>
</p>
</div>
<footer class="tags">none</footer>
</article>
<article class="polyfill gtie9">
<header>
<h2 class="name" id="form validation">form validation </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p>HTML5 has baked in clientside form validation, and polyfills can enable this for legacy browsers as well. Using the defined HTML5 API for constraint validation may be a more maintainable direction than using a jQuery Validation plugin, depending on your team. When detecting this feature, be aware of Safari's half baked support. It does support form validation, but won't highlight invalid fields or present error messages.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://afarkas.github.com/webshim/demos/">webshims</a>, <a href="https://github.com/dperini/nwxforms">nwxforms</a>, <a href="https://github.com/ryanseddon/H5F">H5F</a></p></div>
<p class="links">
<a href="http://caniuse.com/form-validation">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/form-validation.md">Edit this info</a>
</p>
</div>
<footer class="tags">polyfill gtie9</footer>
</article>
<article class="">
<header>
<h2 class="name" id="FormData API">FormData API </h2>
<h3 class="status caution">caution <i></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>XMLHttpRequest Level 2 adds support for the new <a href="http://www.w3.org/TR/XMLHttpRequest2/#interface-formdata">FormData</a> interface,
which provides a way to easily construct a set of key/value pairs representing
form fields and their values, and can be sent using the XMLHttpRequest
<code>send()</code> method. A FormData object can be constructed from an
already existing form or created programmatically.</p>
<p>Sending input values can easily be done already. For instance, the MooTools
framework has a <a href="http://mootools.net/docs/core/Element/Element#Element:toQueryString">toQueryString()</a>
method that can create a query string from any element. What's new with
FormData is that it can send files!</p>
<pre>
var xhr = new XMLHttpRequest()
, file = document.getElementById('myfile')
, fd = new FormData()
fd.append(file.name, file)
xhr.open("POST", '/api/file-upload')
xhr.send(fd)
</pre>
<p><a href="http://www.w3.org/TR/FileAPI/">FileAPI</a> can also be used to send files but you
need to construct the body of the XHR by hand and send it using the <a href="https://developer.mozilla.org/en-US/docs/DOM/XMLHttpRequest#sendAsBinary%28%29">sendAsBinary()</a>
method, which is only implemented in Firefox. This might also use a lot of
memory since the whole content of the file must be read in memory in order
to build the body, whereas FormData sends packets.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/formdata">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/formdata.md">Edit this info</a>
</p>
</div>
<footer class="tags"></footer>
</article>
<article class="fallback">
<header>
<h2 class="name" id="fullscreen">fullscreen </h2>
<h3 class="status caution">caution <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>The Full Screen API is currently only available in the latest versions of Chrome, Firefox and Opera. A jQuery plugin is available which contains an optional fallback to a minimal-chrome browser window when the Full Screen API is unavailable. Use as a progressive enhancement for those select browsers only.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/darcyclarke/jQuery-Fullscreen-Plugin">jQuery Fullscreen Plugin</a></p></div>
<p class="links">
<a href="http://caniuse.com/fullscreen">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/fullscreen.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback</footer>
</article>
<article class="fallback gtie8">
<header>
<h2 class="name" id="geolocation">geolocation </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p><a href="http://code.google.com/p/geo-location-javascript/">geo-location-javascript</a> has hooks into BlackBerry, WebOS, and Google Gears specific APIs. In most cases, you should just not expose Geo features in your app if the feature is not natively present.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://code.google.com/p/geo-location-javascript/">geo-location-javascript</a></p></div>
<p class="links">
<a href="http://caniuse.com/geolocation">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/geolocation.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback gtie8</footer>
</article>
<article class="fallback prefixes gtie8">
<header>
<h2 class="name" id="gradients">gradients </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>We strongly recommend you use the prefixes (<code>-o-</code>, <code>-webkit-</code>, <code>-moz-</code>) when you provide gradients as image values (<code>background</code> or <code>border-image</code>). Do provide a fallback color if you are using this as a value for <code>background</code> so browsers that do not support the gradients can render a solid background color.</p>
<p>We also suggest you drop old WebKit syntax and only use the <a href="https://developer.mozilla.org/en/CSS/-moz-linear-gradient">newer syntax</a> for gradient values and <a href="http://www.broken-links.com/2012/01/11/the-new-and-hopefully-final-linear-gradient-syntax/">not the latest one</a> (yet) until Chrome & Safari start supporting the newer syntax.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/gradients">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/gradients.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback prefixes gtie8</footer>
</article>
<article class="none">
<header>
<h2 class="name" id="grids">grids </h2>
<h3 class="status avoid">avoid <i></i> </h3>
<h4 class="kind css">css</h4>
</header>
<div class="more">
<div class="recco">
<p>The <a href="http://dev.w3.org/csswg/css3-grid-align/">CSS Grid Layout</a> specification supersedes several older ones, and only features an experimental implementation in Internet Explorer 10. Until the specification matures and more implementations exist, we suggest that you avoid using this.</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/grids">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/grids.md">Edit this info</a>
</p>
</div>
<footer class="tags">none</footer>
</article>
<article class="fallback">
<header>
<h2 class="name" id="history">history </h2>
<h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
<h4 class="kind api">api</h4>
</header>
<div class="more">
<div class="recco">
<p>The <code>History</code> API provides a way for JavaScript to change the URL displayed in the browser without reloading the page. There are several approaches to providing a fallback. The simplest is to fall back to page refreshes. Alternatively, the <a href="https://github.com/browserstate/history.js">History.js</a> plugin smooths out some browser implementation differences and provides an optional hashchange fallback for HTML 4 browsers. GitHub uses <a href="http://pjax.heroku.com/">pjax</a> (pushState + ajax).</p>
</div>
<div class="polyfills"></div>
<p class="links">
<a href="http://caniuse.com/history">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/history.md">Edit this info</a>
</p>
</div>
<footer class="tags">fallback</footer>
</article>
<article class="gtie8 polyfill">
<header>
<h2 class="name" id="HTML5 elements">HTML5 elements </h2>
<h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
<h4 class="kind html">html</h4>
</header>
<div class="more">
<div class="recco">
<p>All current browsers, except Internet Explorer 8 and below, support the use of the new HTML5 elements (e.g., <code><header></code>, <code><footer></code>, <code><nav></code>, <code><main></code>, <code><article></code>, <code><section></code>, etc.). However, they aren't always mapped to accessibility APIs as the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria">HTML5 spec</a> requires. Currently <a href="http://html5accessibility.com/">only Firefox does this</a>, but other browsers are implementing the accessibility APIs quickly. In the meantime, <a href="https://github.com/yatil/accessifyhtml5.js">Accessifyhtml5.js</a> maps them correctly.</p>
<p>The notes below only apply to Internet Explorer 8 and below:</p>
<p>The <a href="http://code.google.com/p/html5shiv/">html5shiv</a> enables you to use the new HTML5 elements in your markup (and Modernizr does the exact same by default).</p>
<p>If you insert any of these new elements later on (via AJAX or templating), the html5shiv will handle this for you (as of v3). <a href="http://blog.jquery.com/2011/11/03/jquery-1-7-released/">jQuery 1.7</a> has this functionality baked in.</p>
<p>Lastly, if you need these elements to print correctly, use <a href="https://github.com/aFarkas/html5shiv/blob/master/src/html5shiv-printshiv.js">html5shiv-printshiv.js</a>.</p>
</div>
<div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://code.google.com/p/html5shiv/">html5shiv</a>, <a href="https://github.com/aFarkas/html5shiv/">html5shiv (github)</a>, <a href="https://github.com/yatil/accessifyhtml5.js">accessifyhtml5.js</a></p></div>
<p class="links">
<a href="http://caniuse.com/html5semantic">
View browser share %
</a>
<a href="https://github.com/h5bp/html5please/blob/master/posts/html5semantic.md">Edit this info</a>
</p>