W3C has various consensus statuses for drafts. Many of these are tightly correlated to browser support. Perhaps we could find a clean way to add them without cluttering it up too much.

• https://tools.ietf.org/id/draft-dold-payto-04.html
• https://developer.mozilla.org/en-US/docs/Web/API/PaymentRequest
• https://www.w3.org/TR/payment-handler/
• https://webmonetization.org/
• https://web-payments.org/specs/source/web-commerce-api/
• Others?

Options

• Try fixing it as it exists
• Replace it with CSS Grid

• JPEG XR: Only supported in IE11
• JPEG 2000: Only supported in Safari

Such as like this:

This will help make #31 clearer, which adds a percentage of how many users have the feature available.

ARIA, etc.

Research and add these (and any missing ones) in order of first added date, with the same format: last updated date, element name, and technology:

Get some practice using HTML.

• GIF
• Motion JPEG
• APNG
• Webm
• Ogg
• AV1
• HEVC
• MPEG

Currently the dates are the last time the specs were updated, which feedback shows makes for a confusing experience. Spec start dates should be added in the format 2012-2015, where 2015 is the end date.

Ideally, the spec start date should also link to the first version of the spec that was implemented. Or an article on the history– I'm not sure which yet. However, we can do that separately.

https://www.w3.org/TR/activitystreams-core/#introduction

Would like someone more knowledgable about web security to help.

Possible items:

• TLS (1.0-1.3?)
• CORS
• HSTS
• HSTS Preload
• CSP

First row: So that we have more space for APIs.
Second row: so that it looks like a periodic table, with space between the top section and the bottom one.

Improve colors while satisfying these requirements:

• Darkness and lightness represents the browser support of an API
• Redness represents how active an API's proposal or specification is.

User who needed this: https://news.ycombinator.com/item?id=25415285

• https://drafts.csswg.org/css-content-3/
• if statement
• performance: contain/visibility
• other CSS working drafts?

Easy to use in the HTML markup, example:

                <td class="all">
                    <a href="https://caniuse.com/?search=xhtml"></a>
                    <time><a href="https://www.w3.org/TR/2010/NOTE-xhtml2-20101216/">2010</a></time>
                    <dt><a href="https://www.cnet.com/news/an-epitaph-for-the-web-standard-xhtml-2/">Xhtml</a></dt>
                    <dd><a href="https://www.w3schools.com/html/html_xhtml.asp">XHTML</a></dd>
                </td>

Sometimes an API isn't in Firefox or Safari because they believe that the feature is harmful, and refuse to implement due to privacy or security concerns, such as Web USB: https://mozilla.github.io/standards-positions/#webusb

Other times, Firefox and/or Safari are implementing or considering implementing it, and only Chrome has fully implemented it yet, such as the Badging API: https://mozilla.github.io/standards-positions/#badging.

@codestance, can you help make separate colors for these two cases?

It looks like this on mobile:

@codestance I'm unsure of how to proceed to fix this responsiveness issue, can you help?

Great idea ! A couple of suggestions:

• scale the page so it doesn't scroll horizontally. Maybe:
  meta name="viewport" content="width=device-width, initial-scale=1.0"
  body style="max-width:100%;"
  or something like that.

• the symbols just distract when there already is a well-known acronym. For example, adding "Mail" above "SMTP", or "Hx" above "XHTML", just seems to make clutter.

Wanted: more links to guides, specs, and demos from people even lightly familiar with that technology.

Please comment the best spec, demo, or guide here, or send a pull request if you want to be credited in commits. If you do send a pull request, follow these guidelines:

Spec: Should be linked to from date
Demo or reference: Should be linked to from element name
Guide: Should be linked to from description