n.whatwg.org issues

[annevk]

• The formdata resource is no longer rendered as text/plain.
• The Index listing has ../ as an item.

[foolip]

@sideshowbarker

[annevk]

Is the ../ some kind of nginx-style? Also, what's up with not being able to generate valid HTML in 2017 for these kind of indexes?

[sideshowbarker]

Is the ../ some kind of nginx-style?

It’s the style we get from the default autoindex. But there’s an optional fancyindex we can enable that suppresses the ../ (and that makes the listings interactively sortable).

Also, what's up with not being able to generate valid HTML in 2017 for these kind of indexes?

Indeed. I guess I’ll do a PR against the nginx sources (and the fancyindex sources to, since it has the same problem) to make it generate valid HTML for indexes.

Anyway, I have fancyindex (whatwg/misc-server#14) enabled now, so you can go to, e.g., https://n.whatwg.org/ and https://images.whatwg.org/ and https://resources.whatwg.org/ to see what it looks like.

[annevk]

Looks a little ugly, but not objectionably so.

[annevk]

(Oh, and thanks for looking into this!)

[domenic]

That's way nicer than Apache :). With some extra configuration we could even add our own CSS to make it WHATWG green instead of brown!

[sideshowbarker]

With some extra configuration we could even add our own CSS to make it WHATWG green instead of brown!

Indeed. Raised whatwg/resources.whatwg.org#64 so we don’t forget

[sideshowbarker]

Also, what's up with not being able to generate valid HTML in 2017 for these kind of indexes?

Indeed. I guess I’ll do a PR against the nginx sources (and the fancyindex sources to, since it has the same problem) to make it generate valid HTML for indexes.

Happy to discover that this has already been fixed for fancyindex upstream:

• Default template does not validate against declared document type aperezdc/ngx-fancyindex#52
• aperezdc/ngx-fancyindex@bdaceb6
• aperezdc/ngx-fancyindex@c5deb79
• https://github.com/aperezdc/ngx-fancyindex/releases/tag/v0.4.2

…released only 25 days ago, so we’ll just need to wait for the Debian package to get updated.

[annevk]

This was fixed by whatwg/misc-server@3d3e364.