Skip to content
This repository
tree: b17bfe54b7
Fetching contributors…

Octocat-spinner-32-eaf2f5

Cannot retrieve contributors at this time

file 2307 lines (1878 sloc) 127.255 kb
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 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306
<!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 caution">caution <i>with <b class=fallback>fallback</b></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>CSS Animations are still in flux. The Working Group has <a href="http://www.w3.org/2012/01/13-svg-minutes.html#action02">decided to provide</a> a universal animation spec that would work across CSS, SVG and HTML. For now, 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="&lt;audio&gt;">&lt;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&lt;=4 and Android&lt;=2.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>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 are box sizing issues in Gecko/Firefox, see <a href="https://developer.mozilla.org/En/CSS/Box-sizing#Notes">notes at MDN</a>. Most notable, 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="none">
            <header>
              <h2 class="name" id="calc()">calc() </h2>
              <h3 class="status caution">caution <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Internet Explorer, Chrome and Firefox are the only supporting browsers, which makes using calc() in production tedious given the impact it can have on layout and the consequent breaking of your design on unsupported browsers. We encourage you to use it for experimentation and always use a fallback declaration, so it doesn't break browsers which don't support it.</p>

<p>For now, <code>calc()</code> must always be used after 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); /** Chrome / Safari **/
width: -moz-calc(50% - 20px); /** Mozilla Firefox **/
width: -o-calc(50% - 20px); /** could be calc(), no idea about Opera's plans **/
width: calc(50% - 20px); /** IE 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">none</footer>
          </article>
          
          <article class="gtie8 polyfill">
            <header>
              <h2 class="name" id="&lt;canvas&gt;">&lt;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 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>classList is a relatively new feature which may not be available in older browsers and Internet Explorer. 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 polyfills below 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/toolness/postmessage-proxied-xhr/#readme">postmessage-proxied-xhr</a>, <a href="http://flxhr.flensed.com/">flXHR</a> (requires crossdomain.xml), <a href="https://github.com/eligrey/pmxdr">pmxdr</a> (requires host installed)</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="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="&lt;datalist&gt;">&lt;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>&lt;datalist&gt;</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 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="&lt;details&gt;">&lt;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://caniuse.com/es6">
                  View browser share %
                </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>&lt;input type=file&gt;</code> is rather easy.
Supported in Chrome, Firefox, Opera. Safari is currently missing FileReader support.</p>

<p><a href="https://github.com/Jahdrien/FileReader">FileReader</a> provides useful fallback, based on Flash, jQuery and jQuery UI.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/Jahdrien/FileReader">FileReader</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 &amp; 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="prefixes">
            <header>
              <h2 class="name" id="filters">filters </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Filters are now supported by Safari 6 and Chrome 18+. But, given the lack of support in other browsers, consider waiting for other implementations before use. </p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://css3clickchart.com/#filters">
                  Learn more
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/filters.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">prefixes</footer>
          </article>
          
          <article class="none flexible">
            <header>
              <h2 class="name" id="flexbox">flexbox </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Unfortunately, <a href="http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/">older versions of this spec</a> have been implemented in Gecko, WebKit and Trident. A tutorial covering that spec is <a href="http://www.html5rocks.com/en/tutorials/flexbox/quick/">on HTML5 Rocks</a>.</p>

<p>But <a href="http://dev.w3.org/csswg/css3-flexbox/">the spec</a> has changed significantly. Stephan Hay has <a href="http://www.the-haystack.com/2012/01/04/learn-you-a-flexbox/">written a guide on the new flexbox implementation</a>. However, since this revised spec, the spec underwent more naming changes, which have started to debut in Chrome 22. The spec is now at last call and is considered stable so we expect no more breaking changes.</p>

<p>We recommend you avoid using this until the TR version of the spec finds wide-spread implementation.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p>http://flexiejs.com/</p></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 the <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="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 and Firefox. 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 all the prefixes (<code>-o-</code>, <code>-webkit-</code>, <code>-ms-</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 <a href="http://www.w3.org/TR/css3-images/">the specification</a> hits Candidate Recommendation. </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/balupton/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>&lt;header&gt;</code>, <code>&lt;footer&gt;</code>, <code>&lt;nav&gt;</code>, <code>&lt;article&gt;</code>, <code>&lt;section&gt;</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>
            </div>
            <footer class="tags">gtie8 polyfill</footer>
          </article>
          
          <article class="none prefixes">
            <header>
              <h2 class="name" id="hyphens">hyphens </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p><a href="http://dev.w3.org/csswg/css3-text/#hyphenation">CSS Text Level 3</a> allows you to tell the browser to break words using hyphens. Read about how to effectively use <code>hyphens:auto</code> and <code>word-break</code> in <a href="http://blog.kenneth.io/blog/2012/03/04/word-wrapping-hypernation-using-css/">Word wrapping/hyphenation using CSS</a>.</p>

<p>As there won't by any noticable effects on browsers which don't support the feature, we recommend that you use it without any polyfills or fallbacks. <a href="http://code.google.com/p/hyphenator/">CSS Hyphenator</a> is a polyfill that works on browsers that support the soft hyphen. <a href="https://github.com/Modernizr/Modernizr/issues/312">Modernizr has good support</a> for hyphentation detection. It'd also be wise to read <a href="http://davidnewton.ca/the-current-state-of-hyphenation-on-the-web">The Current State of Hyphenation on the Web
</a>.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/hyphens">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/hyphens.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none prefixes</footer>
          </article>
          
          <article class="gtie9">
            <header>
              <h2 class="name" id="iframe[sandbox]">iframe[sandbox] </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>This attribute enables fine-grained control over the capabilities of a
document housed within an iFrame.</p>

<p>Browser support is not nearly high enough to consider this measure alone
sufficient for sanitizing output. Use this attribute as part of a
defense-in-depth strategy.</p>

<p>Also see <a href="http://weblog.bocoup.com/third-party-javascript-development-future/#iframe-sandbox">more about implementing <code>iframe[sandbox]</code></a> responsibly on Bocoup's blog.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/iframe-sandbox">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/iframe-sandbox.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie9</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="iframe[seamless]">iframe[seamless] </h2>
              <h3 class="status caution">caution <i></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>This attribute instructs browsers to treat the iFrame's content more like inline markup than it would otherwise. Specifically, this means:</p>

<ul>
<li>Hyperlinks navigate the parent context</li>
<li>The parent's stylesheets cascade in (importantly, the inverse is not true)</li>
<li>More "neutral" rendering, roughly equivalent to declaring: <code>scrolling="no" marginwidth="0" marginheight="0" frameborder="0" vspace="0" hspace="0"</code></li>
</ul>

<p>Because the user experience of following hyperlinks is so drastically altered in supporting browsers, use this attribute with caution.</p>

<p>Also see <a href="http://weblog.bocoup.com/third-party-javascript-development-future/#iframe-seamless">more about implementing <code>iframe[seamless]</code></a> responsibly on Bocoup's blog.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/iframe-seamless">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/iframe-seamless.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="polyfill">
            <header>
              <h2 class="name" id="iframe[srcdoc]">iframe[srcdoc] </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>This attribute allows for in-line specification of iframe content.</p>

<p>For non-supporting browsers, you can use <a href="https://github.com/jugglinmike/srcdoc-polyfill">this srcdoc polyfill</a> which utilizes script-targeted URLs to provide this functionality in non-supporing browsers.</p>

<p>Also see <a href="http://weblog.bocoup.com/third-party-javascript-development-future/#iframe-srcdoc">more about implementing <code>iframe[srcdoc]</code></a> responsibly on Bocoup's blog.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/jugglinmike/srcdoc-polyfill">srcdoc polyfill</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/iframe-srcdoc">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/iframe-srcdoc.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill</footer>
          </article>
          
          <article class="fallback gtie8">
            <header>
              <h2 class="name" id="IndexedDB">IndexedDB </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>IndexedDB was a volatile spec for a year, but has settled down. In addition to Chrome and Firefox, IE10 will have it; Opera has not yet implemented it and Safari has not yet committed to it.</p>

<p>The <a href="http://nparashuram.com/IndexedDBShim">IndexedDB Polyfill</a> is a polyfill for the IndexedDB APIs over WebSql. This enables IndexedDB to work on browsers that support WebSql.
<a href="https://github.com/jensarps/IDBWrapper">IDBWrapper</a> helps smooth out the cross-browser differences. You may consider falling back to WebSQL when IndexedDB isn't available, but do keep in mind that WebSQL has been abandoned.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/jensarps/IDBWrapper">IDBWrapper</a>, <a href="http://nparashuram.com/IndexedDBShim">IndexedDB Polyfill</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/indexeddb">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/indexeddb.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback gtie8</footer>
          </article>
          
          <article class="polyfill gtie9">
            <header>
              <h2 class="name" id="&lt;input type=color&gt;">&lt;input type=color> </h2>
              <h3 class="status avoid">avoid <i>with <b class=polyfill>polyfill</b></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>A color input will fall back to a plain text input if it's not supported. So far, only Opera and Chrome Canary support this.</p>

<p>You should probably avoid this until it has support in WebKit, Gecko or IE.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/input-color">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/input-color.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie9</footer>
          </article>
          
          <article class="polyfill gtie9">
            <header>
              <h2 class="name" id="&lt;input type=date&gt;">&lt;input type=date> </h2>
              <h3 class="status caution">caution <i>with <b class=polyfill>polyfill</b></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>There are many date inputs: <code>datetime-local, date, time, month, week</code> that should provide a datepicker to the user. For a long time, WebKit offered a spinner UI on these inputs, but this was an incomplete implementation (and has since been removed).</p>

<p>A few polyfills offer a proper datepicker UI, if the feature is not offered natively.</p>

<p>We suggest you use Modernizr to detect this feature, as it has correctly detected these features, regardless of WebKit's partial implementation or other browser bugs.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://afarkas.github.com/webshim/demos/demos/webforms.html">webshims</a>, <a href="http://www.useragentman.com/blog/2010/07/27/cross-browser-html5-forms-using-modernizr-webforms2-and-html5widgets/">html5widgets</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/input-datetime">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/input-datetime.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie9</footer>
          </article>
          
          <article class="polyfill fallback">
            <header>
              <h2 class="name" id="&lt;input type=number&gt;">&lt;input type=number> </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 number input will fallback to a plain text input if it's not supported.</p>

<p>So far, Chrome, Safari and Opera support it. Jonathan Stipe's <a href="https://github.com/jonstipe/number-polyfill">Number polyfill</a> doesn't need any additional code changes but does require jQuery and CSS to style buttons.</p>

<p>Safari on iOS and the Browser on Android 4.0 (Ice Cream Sandwich) do show number input, but do not use "step", "min" or "max" attributes and neither show increment/decrement buttons.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/jonstipe/number-polyfill">Number polyfill</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/input-number">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/input-number.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill fallback</footer>
          </article>
          
          <article class="polyfill gtie9">
            <header>
              <h2 class="name" id="&lt;input type=range&gt;">&lt;input type=range> </h2>
              <h3 class="status caution">caution <i>with <b class=polyfill>polyfill</b></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>A range input (AKA slider) will fall back to a plain text input if it's not supported.</p>

<p>You can use freqdec's <a href="http://www.frequency-decoder.com/2010/11/18/unobtrusive-slider-control-html5-input-range-polyfill/">Input Range Polyfill</a> or for just Firefox support, Frank Yan's <a href="https://github.com/fryn/html5slider">html5slider</a>.</p>

<p>These polyfills aren't drop-in polyfills, and you'll need to wire them up a little, but your markup can depend on <code>&lt;input type=range&gt;</code> creating a slider.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://www.frequency-decoder.com/2010/11/18/unobtrusive-slider-control-html5-input-range-polyfill/">Input Range Polyfill</a>, <a href="https://github.com/fryn/html5slider">html5slider</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/input-range">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/input-range.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie9</footer>
          </article>
          
          <article class="">
            <header>
              <h2 class="name" id="&lt;input type=search&gt;">&lt;input type=search> </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>A <a href="http://wufoo.com/html5/types/5-search.html">search input</a> will fall back to a plain text input if it's not supported. The standard doesn't specify any behavior for this type, but recommends styling to match the platform's search fields (e.g. with rounded corners on OS X). The style cancels out many CSS styles from being applied, and can be removed with <code>-webkit-appearance: none;</code>. The recommendation here is to use <code>input[type=search]</code> to enhance your forms, so long as you're okay with the styling difference.</p>

<p>While the standard does not specify any behavior, Webkit browsers supply a button to clear the input when it has a value.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/input-search">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/input-search.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags"></footer>
          </article>
          
          <article class="gtie9">
            <header>
              <h2 class="name" id="input[placeholder]">input[placeholder] </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Input placeholders are simply ignored in IE 9 and below. Note that they are only applied when the <strong>type</strong> of the input is <em>text</em>, <em>password</em>, <em>search</em>, <em>tel</em>, <em>url</em>, or <em>email</em>. <em>Textareas</em> can have placeholders, too. Otherwise, it is ignored.</p>

<p><code>input[placeholder]</code> is commonly the first polyfill anyone writes and, as such, there are <a href="http://bit.ly/polyfills">many of them</a>. Password inputs and submit event clearing are among many of the gotchas that catch naive implementations; Mathias's polyfill below handles these cases very well.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/mathiasbynens/jquery-placeholder">Placeholder jQuery Plugin</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/input-placeholder">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/input-placeholder.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie9</footer>
          </article>
          
          <article class="gtie7 polyfill">
            <header>
              <h2 class="name" id="JSON">JSON </h2>
              <h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
              <h4 class="kind js">js</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Crockford's <a href="https://github.com/douglascrockford/JSON-js">JSON2.js</a> is a perfect polyfill that accounts for non-native implementations (basically only IE6 &amp; IE7 at this point). It's robust, well tested and can be used along with the native feature flawlessly.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/douglascrockford/JSON-js">json2.js</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/json">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/json.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie7 polyfill</footer>
          </article>
          
          <article class="gtie7 polyfill">
            <header>
              <h2 class="name" id="localStorage">localStorage </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>Local and session storage are a great way to store data without resorting to cookies. IE8 supported <code>localStorage</code> and <code>sessionStorage</code> so you may not need a polyfill. If you do, Remy's is a piece of cake to implement and use.</p>

<p>This is a simple key/value store, so if you want to store complex data use <code>JSON.parse(str)</code> and <code>JSON.stringify(obj)</code> on your way in and out. There is also no way to know if you exceeded the storage cross-browser, so wrap your store commands in try/catch. Up to 2.5MB is safe to use.</p>

<p>As part of keeping things simple, <code>localStorage</code> has a synchronous API that runs on the main UI thread in browsers; as a consequence of that, a <a href="http://html5doctor.com/storing-data-the-simple-html5-way-and-a-few-tricks-you-might-not-have-known/#comment-17296">race condition</a> can occur if a user has the same site open in multiple windows or tabs running as separate processes. For many applications, that’s never really a problem in practice. But it can cause data corruption—so applications where it’s important to try to ensure that absolutely no data corruption can occur should instead use a more robust storage mechanism such as <code>IndexedDB</code>.</p>

<p>Due to the shortcomings of <code>localStorage</code>, there are calls <a href="http://paul.kinlan.me/we-need-to-kill-off-the-localstorage-api">to stop advocating for and building examples that use it</a>.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://gist.github.com/350433">Remy’s storage polyfill</a>, <a href="http://code.google.com/p/sessionstorage/">sessionstorage</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/localstorage">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/localstorage.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie7 polyfill</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="masks">masks </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p><a href="http://www.webkit.org/blog/181/css-masks/">CSS Masks</a> are not being standardized and are unlikely to ever be. CSS Filters might be your path to salvation.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://css3clickchart.com/#masks">
                  Learn more
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/masks.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="polyfill">
            <header>
              <h2 class="name" id="matchMedia">matchMedia </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>matchMedia provides a JavaScript API to see if a media query will succeed. <a href="https://github.com/paulirish/matchMedia.js/">MatchMedia.js</a> provides a shim for unsupported browsers. If you want a shim that is responsive to window resizing, you can use <a href="http://www.paulrhayes.com/2011-11/use-css-transitions-to-link-media-queries-and-javascript/">this fork</a>, though it's limited to browsers that support CSS Transitions.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/matchmedia">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/matchmedia.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill</footer>
          </article>
          
          <article class="gtie8">
            <header>
              <h2 class="name" id="media queries">media queries </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Media Queries (MQ) work on all modern browsers. OldIE (IE6,7,8) unfortunately do not understand media queries on features, which means none of your CSS within media queries will be parsed by them. We recommend you make peace with that (or use Chrome Frame), but if you absolutely cannot, then you can use <a href="https://github.com/scottjehl/Respond">Respond.js</a> but be aware it has performance overhead that slows down page load.</p>

<p>If you choose a <a href="http://bradfrostweb.com/blog/web/mobile-first-responsive-web-design/">mobile first approach</a>, you'll be targeting smallest screens first, then the different media queries will take effect as the window/device size increases. But if the browser doesn't support media queries and you don't use a polyfill, then the 'mobile first' styles will be applied to OldIE. You can serve a <a href="http://nicolasgallagher.com/mobile-first-css-sass-and-ie/">separate stylesheet for IE to help with this</a>.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/mediaqueries">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/mediaqueries.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie8</footer>
          </article>
          
          <article class="polyfill noie nomobile">
            <header>
              <h2 class="name" id="&lt;menu&gt;">&lt;menu> </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>Firefox has native support for context menus, and using the below polyfill other browsers will be able to do the same.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/medialize/jQuery-contextMenu">contextMenu</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/menu">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/menu.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill noie nomobile</footer>
          </article>
          
          <article class="polyfill noie nomobile">
            <header>
              <h2 class="name" id="&lt;meter&gt;">&lt;meter> </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">
                
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://gist.github.com/667320">meter-polyfill</a>, <a href="https://github.com/xjamundx/HTML5-Meter-Shim">jQuery shim</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/meter">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/meter.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill noie nomobile</footer>
          </article>
          
          <article class="polyfill ie6 gtie6">
            <header>
              <h2 class="name" id="Microdata DOM API">Microdata DOM 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>Microdata is a new lightweight semantic meta-syntax. Using attributes, we can define nestable groups of name-value pairs of data, called microdata, which are generally based on the page's content. It gives us a whole new way to add extra semantic information and extend HTML5. Microdata is already being used by google to extract semantic meta data from your webpage.</p>

<p>The Microdata DOM API is helpful because you can manipulate items and properties on a page programmatically, perhaps to present the information in a searchable/filterable manner, or deliver it to another application somewhere else.</p>

<p>It's supported by Opera and <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=591467">also being implemented by Mozilla</a></p>

<p>IE6+ support can be done using <a href="https://github.com/termi/ES5-DOM-SHIM">this ES5/DOM shim</a></p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/termi/Microdata-JS">microdata shim</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/microdata-domapi">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/microdata-domapi.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill ie6 gtie6</footer>
          </article>
          
          <article class="gtie6">
            <header>
              <h2 class="name" id="min/max-width/height">min/max-width/height </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p><code>min-width</code>, <code>max-height</code>, etc are supported everywhere as of IE7. The <a href="http://www.dustindiaz.com/min-height-fast-hack/">min-height fast hack</a> has long been a reliable way of implementing min-height, but as many have sunsetted IE6 support, you likely don't need to worry about fallback anymore.</p>

<p>Use all you like without fallback; certainly do not use CSS expressions to mimic this behavior.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/minmaxwh">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/minmaxwh.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie6</footer>
          </article>
          
          <article class="prefixes gtie9 columns">
            <header>
              <h2 class="name" id="multicolumn">multicolumn </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+), and Opera support CSS Multi-column Layout without vendor prefixes, so you only need prefixed versions for <code>-webkit-</code> and <code>-moz-</code>.</p>

<p>We recommend you do not polyfill this and let it fall back to single column text.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/multicolumn">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/multicolumn.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">prefixes gtie9 columns</footer>
          </article>
          
          <article class="fallback gtie8">
            <header>
              <h2 class="name" id="multiple backgrounds">multiple backgrounds </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>Multiple backgrounds will be <a href="http://snook.ca/archives/html_and_css/multiple-bg-css-gradients">completely ignored</a> when they aren't supported. If you can use a simple background color, make sure to declare <code>background-color: &lt;color&gt;</code> on the element before declaring your multiple backgrounds. Alternatively, you can also set an image as a background with <code>background-image</code> and override it with a second background declaration. We strongly recommend you don't polyfill this.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/multibackgrounds">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/multibackgrounds.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback gtie8</footer>
          </article>
          
          <article class="fallback gtie9">
            <header>
              <h2 class="name" id="offline">offline </h2>
              <h3 class="status caution">caution <i>with <b class=fallback>fallback</b></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>If Application Cache isn't available natively, there is no way to mimic it. Only supporting browser will be able to load a page while offline. Still, many apps can make use of local storage to enable offline interaction if the page is already open.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/offline">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/offline.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback gtie9</footer>
          </article>
          
          <article class="polyfill">
            <header>
              <h2 class="name" id="ol[reversed]">ol[reversed] </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>Please use the below polyfill, as WebKit is the only engine that supports it right now.
Also see <a href="http://www.impressivewebs.com/reverse-ordered-lists-html5/">Louis's ol[reversed] post</a>.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://gist.github.com/1671548">ol reversed polyfill</a>, <a href="https://github.com/impressivewebs/HTML5-Reverse-Ordered-Lists">HTML5 reverse ordered lists</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/ol-reversed">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/ol-reversed.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill</footer>
          </article>
          
          <article class="gtie8">
            <header>
              <h2 class="name" id="opacity">opacity </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>CSS3 opacity allows you to modify the opacity of HTML elements. It is safe to use. For IE6-IE8, use the proprietary "filter" property to achieve the same effect.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/opacity">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/opacity.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie8</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="paged media">paged media </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>This specification is actively under development and thus still in flux. We recommend you wait until it has matured, and multiple implementations are available.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://css3clickchart.com/#paged-media">
                  Learn more
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/paged-media.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="fallback noie">
            <header>
              <h2 class="name" id="pointer events">pointer events </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>Pointer events are available in SVG and CSS. All modern browsers support them in SVG, but IE and Opera do not support them in CSS yet. There is a <a href="https://github.com/Modernizr/Modernizr/blob/master/feature-detects/css-pointerevents.js">modernizr plugin</a> to detect support, which can be used to implement a JavaScript interceptor for elements which require pointer events to be disabled.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/pointer-events">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/pointer-events.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback noie</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="position:fixed">position:fixed </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Fixed positioning isn't supported in IE6, but is fine in IE7 and everywhere else (<a href="http://bradfrostweb.com/blog/mobile/fixed-position/">except mobile, which is described at length here</a>). </p>

<p>Use fixed positioning all you like, but you may want to check its behavior in mobile browsers afterward. There is a <a href="https://github.com/Modernizr/Modernizr/issues/167#issuecomment-2155861">messy feature detect</a> if you'd like it.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/css-fixed">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/css-fixed.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="api">
            <header>
              <h2 class="name" id="postMessage">postMessage </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p><code>postMessage</code> is present in IE8 and up, but if you need robust support for cross-frame and cross-domain communication, use <a href="http://easyxdm.net/wp/">EasyXDM</a></p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://easyxdm.net/wp/">EasyXDM</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/postmessage">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/postmessage.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">api</footer>
          </article>
          
          <article class="polyfill gtie9">
            <header>
              <h2 class="name" id="&lt;progress&gt;">&lt;progress> </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>Go read <a href="http://www.useragentman.com/blog/2012/01/03/cross-browser-html5-progress-bars-in-depth/">Cross Browser HTML5 Progress Bars In Depth
</a>. :)</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/progress">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/progress.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie9</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="pseudo elements">pseudo elements </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>The pseudo-element notation was updated to use a double colon - <code>::</code> - in the CSS3 Selectors module. The CSS module requires that browsers support both the single and double colon notations for the pseudo-elements introduced in CSS1 and CSS2 - <code>:first-line</code>, <code>:first-letter</code>, <code>:before</code> and <code>:after</code>. Therefore, if you intend to support IE8+, you should use the earlier single colon notation. </p>

<p>When adding generated content to your page with <code>:before</code> and <code>:after</code>, make sure that it is only for presentation and not to add content that should be included in the HTML source, as it may not be accessible.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/pseudo-elements">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/pseudo-elements.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="regions">regions </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>CSS Regions is in active development. As a result, the syntax is in flux. A polyfill based on an older syntax exists, but we recommend you hold your horses till this spec sees some stability and 3 or more implementations.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/regions">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/regions.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="polyfill gtie9">
            <header>
              <h2 class="name" id="requestAnimationFrame">requestAnimationFrame </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><a href="http://paulirish.com/2011/requestanimationframe-for-smart-animating/">requestAnimationFrame is recommended</a> for animation as it's battery and power friendly and allows the browser to optimize the performance of your animations. </p>

<p>The spec has gotten some fixes and settled down. In addition to Chrome and Firefox, IE10 will have it.</p>

<p>An interesting usecase: If you have vertical parallax that changes on scroll, you can consider using rAF instead of binding to a <code>window</code>'s scroll event. In this way, you'd just ask for <code>window.scrollTop</code> on your rAF callback and take action. This will give you the smoothest animations possible.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://gist.github.com/1579671">requestAnimationFrame polyfill</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/requestanimationframe">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/requestanimationframe.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie9</footer>
          </article>
          
          <article class="fallback">
            <header>
              <h2 class="name" id="&lt;ruby&gt;">&lt;ruby> </h2>
              <h3 class="status use">use <i>with <b class=fallback>fallback</b></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>If you are using the Ruby element you don't need a script-based fallback, but you can provide a CSS-based set of good defaults.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://www.useragentman.com/blog/2010/10/29/cross-browser-html5-ruby-annotations-using-css/">Cross-browser Ruby</a>, <a href="http://sideshowbarker.net/2009/11/13/html5-ruby/#comment-3388">basic fallback</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/ruby">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/ruby.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback</footer>
          </article>
          
          <article class="fallback gtie6">
            <header>
              <h2 class="name" id="selectors">selectors </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>Most CSS Selectors are supported from IE7 onwards, so you should be safe to use them. But do note that, on browsers that do not support these selectors, a whole rule will be detected as invalid if these unsupported selectors are present. For example, in IE6 <code>#main, p:first-child {}</code> would be invalid because it is unable to understand <code>p:first-child</code>. We strongly recommend you do not try to polyfill this, but if you do need one, you can use <a href="http://selectivizr.com/">Selectivizr</a>.</p>

<h4>When you sunset IE6 support, you can use:</h4>

<ul>
<li><code>tr &gt; td</code> : Immediate descendant (child) selector.</li>
<li><code>dt + dd</code> : next sibling selector*</li>
<li><code>dt ~ dd</code> : any following sibling</li>
<li><code>div[attr]</code> and <code>img[src$=png]</code> : Attribute selector (starts with, ends with, contains).</li>
<li><code>p:first-child</code>*</li>
<li><code>div:hover</code> and <code>:hover</code> state on all non-<code>&lt;a&gt;</code>'s</li>
<li><code>li.food.vegetable</code> : without worrying about the <a href="http://paulirish.com/2008/the-two-css-selector-bugs-in-ie6/">chained classes bug</a></li>
</ul>

<p>* IE7-8 don't update styles properly when elements are manipulated with JS. Usually you have to force the browser to redraw (e.g. hide and show parent element).</p>

<h4>When you sunset IE7 support, you can use:</h4>

<ul>
<li><code>:before, :after</code> and generated content</li>
<li><code>:focus</code> for elements with current focus</li>
<li><a href="http://www.w3.org/TR/selectors/#lang-pseudo"><code>:lang(C)</code></a> which targets an element based on language</li>
</ul>

<h4>When you sunset IE8 support, you can use:</h4>

<ul>
<li>These very useful selectors: <a href="http://css-tricks.com/how-nth-child-works/"><code>:nth-child(n)</code></a>, <code>:last-child</code>, <code>:target</code>, <code>:not(s)</code>, <code>:enabled</code>, <code>:disabled</code>, <code>:checked</code>, <code>::selection</code></li>
<li>These ones, too: <code>:root</code>, <code>:nth-last-child(n)</code>, <code>:nth-of-type(n)</code>, <code>:nth-last-of-type(n)</code>, <code>:first-of-type</code>, <code>:last-of-type</code>, <code>:only-child</code>, <code>:only-of-type</code>, <code>:empty</code></li>
</ul>

<!--

Resources:

* http://coding.smashingmagazine.com/2009/10/14/css-differences-in-internet-explorer-6-7-and-8/
* http://www.bennadel.com/blog/2306-What-CSS-Properties-Are-Supported-When-You-Drop-IE6-Support.htm
* http://analogysoft.com/learning/ui-hulk-out/#beyondie6
* http://msdn.microsoft.com/en-us/library/cc351024(v=vs.85).aspx#selectors
* http://www.quirksmode.org/css/contents.html
* http://www.impressivewebs.com/browser-support-css3-selectors/

[].forEach.call( document.querySelectorAll('td'), function(elem){
if (elem.innerText.trim() == 'No') elem.style.backgroundColor = 'red';
if (elem.innerText.trim() == 'Yes') elem.style.backgroundColor = 'green';
});

-->
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/selectors">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/selectors.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback gtie6</footer>
          </article>
          
          <article class="">
            <header>
              <h2 class="name" id="style[scoped]">style[scoped] </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p><a href="http://css-tricks.com/saving-the-day-with-scoped-css/">Scoped stylesheets</a> are still in active development. While you can experiment with them in Chrome Canary (type <code>about:flags</code> in Chrome's address bar), there is no stable version of any browser supporting this now. </p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/scoped-css">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/scoped-css.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags"></footer>
          </article>
          
          <article class="gtie8 polyfill">
            <header>
              <h2 class="name" id="&lt;svg&gt;">&lt;svg> </h2>
              <h3 class="status use">use <i>with <b class=polyfill>polyfill</b></i> </h3>
              <h4 class="kind svg">svg</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>SVG has had good support for several years in most browsers, except for Internet Explorer. IE9 brings support, which means for oldIE you can use <a href="http://code.google.com/p/svgweb/">SVGWeb</a> as a polyfill, or create SVG dynamically via <a href="http://raphaeljs.com/">Raphael</a> (which uses a VML fallback). </p>

<p>For Android Browser support, you can use <a href="http://code.google.com/p/canvg/">CanVG</a>. Meanwhile <a href="http://mbostock.github.com/d3/">D3.js</a> is an SVG and DOM library for data visualization.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://code.google.com/p/svgweb/">SVGWeb</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/svg">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/svg.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie8 polyfill</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="text-overflow">text-overflow </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Text overflow is most commonly used for <code>text-overflow: ellipsis</code>. Per Firefox 7, all modern browsers now support this property prefixless and you should use it. On unsupported browsers, it merely does not render the ellipsis, so we recommend that you do not use a polyfill. However, there is a <a href="http://www.bramstein.com/projects/text-overflow/">jQuery plugin</a> in the unlikely event of you needing one. </p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/text-overflow">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/text-overflow.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="gtie9">
            <header>
              <h2 class="name" id="text-shadow">text-shadow </h2>
              <h3 class="status use">use <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>All modern browsers support text-shadow except IE. Since it's mostly used for decorative purposes, we do not recommend using a polyfill; just make sure the text is still legible without a text-shadow. We also advise you to avoid large text-shadows because they can have a negative impact on performance.</p>

<p>Sometimes you may do light/transparent text with an invert text-shadow. In these cases, we recomend to feature detect (with Modernizr) so you can provide solid color <code>.no-textshadow</code> fallback styling.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/text-shadow">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/text-shadow.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">gtie9</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="text-stroke">text-stroke </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind css">css</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Text stroke, which adds an outline or stroke to text, is only supported by WebKit. Text stroke has never been part of a CSS specification and should be avoided.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/text-stroke">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/text-stroke.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
          <article class="polyfill gtie9 webvtt">
            <header>
              <h2 class="name" id="&lt;track&gt;">&lt;track> </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://www.html5rocks.com/en/tutorials/track/basics/">The <code>&lt;track&gt;</code> element</a> provides a mechanism of showing captions/subtitles and/or associated metadata with <code>&lt;audio&gt;</code> or <code>&lt;video&gt;</code>. The file format the <code>&lt;track&gt;</code> element uses is called WebVTT. Browser support for both is in progress: complete in IE10pp4, ongoing in Webkit, unknown in Opera. A polyfill is a wise choice; Captionator is the most complete and well supported. More at <a href="http://blog.gingertech.net/2011/06/27/recent-developments-around-webvtt/">Sylvia Pfeiffer's blog</a>.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://captionatorjs.com/">captionator.js</a></p></div>

              <p class="links">
              
                <a href="https://developer.mozilla.org/en/HTML/Element/track#Compatibility">
                  Learn more
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/track.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie9 webvtt</footer>
          </article>
          
          <article class="fallback prefixes">
            <header>
              <h2 class="name" id="transforms">transforms </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 you use all the right prefixes (<code>-o-</code>, <code>-webkit-</code>, <code>-ms-</code>, <code>-moz-</code>). If your transforms destroy the readability of your site on browsers that do not support them, use Modernizr's <code>no-csstransforms</code> class to adjust the design so that the text remains readable. In the unlikely event of you needing a polyfill for unsupported browsers, use <a href="https://github.com/pbakaus/transformie">Transformie</a> or <a href="http://www.useragentman.com/blog/csssandpaper-a-css3-javascript-library/">CSSSandpaper</a>.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/transforms">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/transforms.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback prefixes</footer>
          </article>
          
          <article class="fallback prefixes">
            <header>
              <h2 class="name" id="transitions">transitions </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>Most of the time, transitions just add to the experience and are not necessary for a usable experience. If there is any critical interaction that requires transitions to be present, we recommend you provide an alternative experience for users on browsers that do not support this feature by feature detecting its presence.
Note that you need to use all the usual prefixes to make this work in all browsers (<code>-o-</code>, <code>-webkit-</code>, <code>-moz-</code>, <code>-ms-</code>).</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/transitions">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/transitions.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback prefixes</footer>
          </article>
          
          <article class="polyfill gtie8">
            <header>
              <h2 class="name" id="&lt;video&gt;">&lt;video> </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>Do note you need to supply your video in various formats to cater to all browsers and fallbacks&mdash;<a href="http://www.mirovideoconverter.com/">Miro Video Converter</a> makes this trivial. H264 and WebM cover all browsers (except Firefox 3.6 which needs Ogg Theora). Use the above polyfill or gracefully handle all cases without any scripting, as explained by Kroc Camen in <a href="http://camendesign.com/code/video_for_everybody">Video for Everybody</a>.</p>

<p>There is also an incredibly useful service called <a href="http://vid.ly">vid.ly</a> which converts video online into all necessary formats and provides a short url that detects your browser/hardware and sends the correct format. <a href="http://archive.org">Archive.org</a> also converts MP4 videos uploaded to OGG automatically, and does the same with audio.</p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="http://mediaelementjs.com/">mediaelementjs</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/video">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/video.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill gtie8</footer>
          </article>
          
          <article class="fallback gtie9">
            <header>
              <h2 class="name" id="Web Workers">Web Workers </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>Web Workers can parallelize computationally heavy operations very well, freeing up the UI thread to respond to user input. Depending on what <a href="http://stackoverflow.com/questions/2773682/what-are-the-use-cases-for-web-workers/2774022#2774022">use case</a> you have for workers, you may choose not to offer that feature if workers aren't present, or to <a href="http://www.nczonline.net/blog/2009/01/13/speed-up-your-javascript-part-1/">chunk it up</a> and put it on the UI thread.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/webworkers">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/webworkers.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback gtie9</footer>
          </article>
          
          <article class="fallback">
            <header>
              <h2 class="name" id="WebGL">WebGL </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>There are polyfills and plugins to enable WebGL for IE, but you <a href="http://blog.virtualglobebook.com/2011/10/webgl-in-internet-explorer.html">probably shouldn't use them</a>. Use WebGL if it's present, else point the user to <a href="http://get.webgl.org/">get.webgl.org</a>.</p>

<p>You can also offer to the user to install <a href="http://code.google.com/chrome/chromeframe/">Google Chrome Frame</a> if they just want a plugin. Nearly all WebGL demos use GCF if it's available.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/webgl">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/webgl.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">fallback</footer>
          </article>
          
          <article class="">
            <header>
              <h2 class="name" id="WebP">WebP </h2>
              <h3 class="status caution">caution <i></i> </h3>
              <h4 class="kind html">html</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>WebP is an image format that's designed to be provide high quality photographic imagery through smaller filesizes than JPEG. It's supported natively in Chrome, Android, and Opera. Through the <a href="https://github.com/antimatter15/weppy">weppy</a> polyfill you can pick up Firefox support.</p>

<p>WebP alpha support is available in Chrome 22 (along with lossless). You can detect alpha support with a <code>onload</code>/<code>onerror</code> handlers, though there is <a href="https://github.com/antimatter15/weppy/issues/2">discussion</a> about giving weppy a firstclass support for alpha+fallback.</p>

<p>For now, Modernizr detects WebP support and you can manage your own fallback to jpeg.</p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/webp">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/webp.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags"></footer>
          </article>
          
          <article class="polyfill prefixes">
            <header>
              <h2 class="name" id="WebSockets">WebSockets </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>Making your app real-time is a huge boost and <a href="http://dev.w3.org/html5/websockets/">WebSockets</a> give you the ability to add bi-directional communication over a persistent connection to your application to increase interactivity and user engagement.</p>

<p><a href="https://github.com/gimite/web-socket-js">web-socket-js</a> is a natural polyfill for the JavaScript WebSocket API transferring data through Flash Sockets when WebSockets aren't available.</p>

<p>To use native WebSockets in Firefox, the prefixed MozWebSocket should be used. However, Firefox 11 will support the <a href="http://tools.ietf.org/html/rfc6455">IETF standard</a> without the prefix.</p>

<p>As a word of caution, the protocol backing the Web Socket API has become an <a href="http://tools.ietf.org/html/rfc6455">IETF standard</a>, but Safari has not yet implemented the (secure) new version. It is recommended forcing an alternative on Safari or disabling WebSockets on Safari for now.</p>

<p>To make websockets easier to use there are multiple server-side framework solutions. These frameworks generally provide fallback transports (HTTP long polling, HTTP streaming, ajax polling) to support non-websocket browsers. However be prepared to tune the fallback solutions in order to meet the needs of your app. </p>

<p><a href="https://github.com/sockjs">Sockjs</a> is one a framework which emulates the WebSocket API in browsers and has server implementations for node.js, Ruby, Erlang or tornado. </p>

<p><a href="http://socket.io/">Socket.io</a> is a Node.js framework that helps with downlevel transports for browsers lacking native WebSocket support (and supports IE6+).</p>

<p>XSockets is a .NET+JavaScript framework that handles fallback via Flash and Silverlight.</p>

<p>For more information see the <a href="http://www.leggetter.co.uk/real-time-web-technologies-guide#self-hosted">Full list of possible server-side websocket solutions</a></p>
              </div>
              <div class="polyfills"><b>Recommended polyfills: </b><p><a href="https://github.com/gimite/web-socket-js">web-socket-js</a></p></div>

              <p class="links">
              
                <a href="http://caniuse.com/websockets">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/websockets.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">polyfill prefixes</footer>
          </article>
          
          <article class="none">
            <header>
              <h2 class="name" id="WebSQL DB">WebSQL DB </h2>
              <h3 class="status avoid">avoid <i></i> </h3>
              <h4 class="kind api">api</h4>
            </header>
            <div class="more">
              <div class="recco">
                <p>Although it initially found favor as a clientside database API, it has now <a href="http://www.w3.org/TR/webdatabase/#status-of-this-document">been abandoned</a> in favor of IndexedDB. We therefore recommend that you do not use WebSQL. </p>
              </div>
              <div class="polyfills"></div>

              <p class="links">
              
                <a href="http://caniuse.com/websql">
                  View browser share %
                </a>
              
                <a href="https://github.com/h5bp/html5please/blob/master/posts/websql.md">Edit this info</a>
              </p>
            </div>
            <footer class="tags">none</footer>
          </article>
          
        </section>
      <h2 id="noitems" class="visuallyhidden">No items met your search =(</h2>
    </div>
    <footer>
      <p>HTML5 Please is a community project (<a href="https://github.com/h5bp/html5please/">contribute on github!</a>) from the people behind <a href="http://html5boilerplate.com">HTML5 Boilerplate</a>, <a href="http://modernizr.com">Modernizr</a> &amp; <a href="http://css3please.com">CSS3 Please</a>.</p>
      <p class="builders"> <a href="http://twitter.com/divya"><img src="http://api.twitter.com/1/users/profile_image/divya?size=normal" alt="Divya Manian"><b>Divya</b> Manian</a> <a href="http://twitter.com/paul_irish"><img src="http://api.twitter.com/1/users/profile_image/paul_irish?size=normal" alt="Paul Irish"><b>Paul</b> Irish</a> <a href="http://twitter.com/tbranyen"><img src="http://api.twitter.com/1/users/profile_image/tbranyen?size=normal" alt="Tim Branyen"><b>Tim</b> Branyen</a> <a href="http://twitter.com/connor"><img src="http://api.twitter.com/1/users/profile_image/connor?size=normal" alt="Connor Montgomery"><b>Connor</b> Montgomery</a> <a href="http://raynos.org/blog/"><img src="http://gravatar.com/avatar/d840cb1fb7e828284011cc08f40a1015?s=48"><b>Jake</b> Verbaten</a> <a href="https://github.com/h5bp/html5please/contributors">&amp; more</a>
      </p>
    </footer>

    <!-- all of these ... -->
    <script src="js/libs/augment.js"></script>
    <script src="js/libs/list.js"></script>
    <script src="js/libs/classList.js"></script>
    <script src="js/script.js"></script>
     <!-- are NORMALLY compiled (with source map) into...

<script src="js/script.min.js"></script>

.. but not today -->


    <script>
        var _gaq=[['_setAccount','UA-17904194-3'],['_trackPageview'],['_trackPageLoadTime']];
        (function(d,t){var g=d.createElement(t),s=d.getElementsByTagName(t)[0];
        g.src=('https:'==location.protocol?'//ssl':'//www')+'.google-analytics.com/ga.js';
        s.parentNode.insertBefore(g,s)}(document,'script'));
    </script>
  </body>
</html>
Something went wrong with that request. Please try again.