Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Further removing of ’ based on #128 #130

Merged
merged 1 commit into from

2 participants

@Gavrisimo

Ok, this is the last one i promise. :)

Something is wrong with my git setup here, when i push to my fork i don't see my github user name, i see "unknown". So i had to use github.com to edit these files.

I think this is last file that had , and not '.

Cheers!

Milos Gavrilovic Further removing of ’ based on #128
Ok, this is the last one i promise. :)
18c69d1
@beverloo
Collaborator

Alright. It'd be great if you could combine such edits in a single commit, in the future. Cheers!

@beverloo beverloo merged commit 5afff1b into h5bp:master
@Gavrisimo

Of course, like i said my git setup here is a bit funky(i have no idea why O_o), and I didn't want to risk bringing funkiness to this project. =D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Commits on Feb 8, 2012
  1. Further removing of ’ based on #128

    Milos Gavrilovic authored
    Ok, this is the last one i promise. :)
This page is out of date. Refresh to see the latest.
Showing with 1 addition and 1 deletion.
  1. +1 −1  posts/html5-sectioningelements.md
View
2  posts/html5-sectioningelements.md
@@ -4,7 +4,7 @@ tags: gtie8 polyfill
kind: html
polyfillurls: [html5shiv](http://code.google.com/p/html5shiv/), [html5shiv (github)](https://github.com/aFarkas/html5shiv/), [accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js)
-All current browsers, except Internet Explorer 8 and below, support the use of the new HTML5 elements (e.g., `<header>`, `<footer>`, `<nav>`, `<article>`, `<section>`, etc.). However, they aren’t always mapped to accessibility APIs as the [HTML5 spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria) requires. Currently [only Firefox does this](http://html5accessibility.com/), but other browsers are implementing the accessibility APIs quickly. In the meantime, [Accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js) maps them correctly.
+All current browsers, except Internet Explorer 8 and below, support the use of the new HTML5 elements (e.g., `<header>`, `<footer>`, `<nav>`, `<article>`, `<section>`, etc.). However, they aren't always mapped to accessibility APIs as the [HTML5 spec](http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria) requires. Currently [only Firefox does this](http://html5accessibility.com/), but other browsers are implementing the accessibility APIs quickly. In the meantime, [Accessifyhtml5.js](https://github.com/yatil/accessifyhtml5.js) maps them correctly.
The notes below only apply to Internet Explorer 8 and below:
Something went wrong with that request. Please try again.