Hi! I would like to help with the translation to Spanish if it's possible. Could you show me how can I help? :D

Url: http://htmlreference.io/element/ins/
It explains page from del

Hello,

I cloned the repo and then when I tried to just run it offline in the browser (no internet available where I'm going) - all I get is this:

**--- route: index --- {% include favicons.html %}
{{site.title}} icon {{site.title}} type
{% include carbon.html %}
{{site.subtitle}}
Learn by example: htmlreference.io is a free guide to HTML. It features all elements and attributes.

{% include social/button-twitter.html %} {% include social/button-facebook.html %}
{% include ff.html %}
Collections: Base elements Forms Lists Semantic Tables
{% include components/finder.html %}
{% include sister.html %} {% include modals/share.html %} {% include google-fonts.html %} {% include noscript.html %}**

Obviously this is some sort of server side generated markup, but no where in the readme it mentions how to install it.

Thanks,
Mark

Every time I visit the page of a tag, I have to re-scroll the sidebar and find the next tag link. It couldn't be better if there were two navigate buttons in every page's bottom. Thank you!

cf https://www.w3.org/International/questions/qa-b-and-i-tags
Basically, they have some semantic, but strong and em should be used instead.

I see that .example-output and .example-code is empty in td, th, tr tags.

Links

1. td
2. th
3. tr

@jgthms, hi!

Do you prefer to add type="button" here – http://htmlreference.io/element/button/ ?

As for me it is useful attribute value for semantic.
If you allow I could prepare the pull request.

Link to SPEC

There are many HTML tags in examples. It would be awesome if every tag linked to its own page. For example, being able to click the <br> tag in this page to get to this page.

Good day, @jgthms

I hope you are doing well. I’ve seen your new project http://htmlreference.io. Good job, my congrats. I’ve found interesting side effect in blocks with code example when you try to hover to social icons. To see more details, please follow this link http://take.ms/v1e9P. For fixing this side effect you can add to .highlight this rule transform: translateZ(0); This solution also will avoid repainting of part of the page.

Looking forward to hearing from you soon.

Best regards,
Vitaly

WHATWG source

HTML Standard

WHATWG definition

The address element represents the contact information for its nearest article or body element ancestor. If that is the body element, then the contact information applies to the document as a whole.

The address element must not be used to represent arbitrary addresses (e.g. postal addresses), unless those addresses are in fact the relevant contact information. (The p element is the appropriate element for marking up postal addresses in general.)

The address element must not contain information other than contact information.

WHATWG example

<ADDRESS>
 <A href="../People/Raggett/">Dave Raggett</A>,
 <A href="../People/Arnaud/">Arnaud Le Hors</A>,
 contact persons for the <A href="Activity">W3C HTML Activity</A>
</ADDRESS>

Your source

HTML Reference

Your definition

The address Defines a block for contact information.

Your example

<address>
  Infinite Loop,<br>
  Cupertino, CA<br>
  95014, USA
</address>

Key differences

Your example defines a postal address while ```address`` 's semantic is defining contact information.

The sidebar links for elements look like: https://htmlreference.io/element/article.

If I click on that link, it 301 redirects to http://htmlreference.io/element/article/ (note HTTP), then to https://htmlreference.io/element/article/ (note HTTPS and a trailing slash). It would be much faster to load pages if the sidebar linked directly to the final URL.

When is described the "X-UA-Compatible" in the URL https://htmlreference.io/base/, There a verison instead of version.

""X-UA-Compatible"
Defines which Internet Explorer verison the web page should be rendered as."

Hi, @jgthms.
Thanks for your nice work of this excellent reference.
But, I wonder why the tag <label> are not in the Forms.

First of all thanks for the awesome resource! I found some inaccuracy in the docs.

a tag can be used without href attribute.

Quote from specification:

If the a element has no href attribute, then the element represents a placeholder for where a link might otherwise have been placed, if it had been relevant, consisting of just the element’s contents.

I can submit PR if you think this page is worth to update.

Of course many HTML elements have "semantics", but those who are not special-purpose (form elements, media elements…) and are used to group or mark content with meaning include:

• blockquote
• h1 … h6
• abbr, cite (not less semantic than time)
• em, strong
• etc.

Maybe this section could be replaced by a "Structure" section that focuses on elements used to describe the structure of a document or app, whether they are HTML4 or HTML5 elements. That would include things like:

• head, body (could be useful)
• h1 … h6
• header, footer, main, section, aside, article
• nav

And maybe leave out figure, figcaption, mark, time, blockquote.

Plz add a inline-block section. img & input are inline-block tags

It'd be great to see a link to caniuse.com on each page to display some browser coverage for each element type, especially stuff that's experimental

i.e. http://caniuse.com/#search=picture

Hi!

I'm not sure if it conflicts with other CSSs in other pages because I don't know the project but this works for the main/index page:

#finder-list .finder-item:nth-child(even) {
    background: #CCC;
}

Regards, Rodrigo.