New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

specified mapping of h1-h6 does not reflect implementations #116

Closed

stevefaulkner opened this issue Jan 26, 2018 · 1 comment

Contributor

stevefaulkner commented Jan 26, 2018

We will need to change the mapping for h1-6 to reflect how the role/level is actually implemented in browsers currently.

stevefaulkner mentioned this issue

Suggest adding a warning about outline algorithm whatwg/html#83

Closed

Contributor

asurkov commented Jan 26, 2018

for the record, firefox always returns a level corresponding to a tag name, ie. 1 for h1, 2 for h2.

stevefaulkner closed this as completed in

ee3f324

jasonkiss added a commit that referenced this issue


          Change log entries for recent fixes

210c7ec

Log fixes for issues #24, #116, #2

Jym77 mentioned this issue

Default level of h1-h6 and nested sectioning #268

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment