When you remove JavaScript, what continues to work?...

[HUGS] getimiskon :OwOid: :blobcatgooglywtf: :verified_neko:

@dillo :blobcatheart:

23 June at 19:13 | Open on fedi.getimiskon.xyz

Koutsie :unverified:

@dillo hell yeahhhh

23 June at 19:13 | Open on layer8.space

Athena L.M.

@dillo Your "D" grade should be an "F" grade, and probably red instead of grey.

23 June at 19:23 | Open on solarpunk.moe

DELETED

@dillo it's good, clean and uncluttered.

23 June at 19:33 | Open on swiss.social

オツユグ

@dillo reminds me of the "anybrowser" thing

23 June at 19:43 | Open on pouet.chapril.org

valkyrie_pilot

@dillo one thing i’ve noticed that kind of sucks is just how bad the hacks are that you need to do certain things without javascript, it really sucks. I wish they gave html + css more power, tbh.

23 June at 19:44 | Open on social.treehouse.systems

Seirdy

@dillo This page at the time of writing grades websites’ progressive enhancement based on their ability to work without JavaScript. Everything, not just JavaScript, should be progressive enhancements.

HTML elements already have progressive enhancement built-in. CSS, JS, and embedded content should be progressively enhanced too. The page should make sense without scripts and styles, alt-text should be available in the absence of embedded media, etc. We shouldn’t put scripting on a pedestal above everything else.

I suggest replacing references to JavaScript with references to non-HTML content. See also: “curlable” on the IndieWeb wiki.

A more minor piece of feedback: I’d suggest re-sizing the badges to 88-by-31 pixels if possible. It’s a very popular size for badges; at these dimensions, they would look good alongside others of the same size (examples from the W3C).

Originally posted on seirdy.one: See original (POSSE).

@dillo This page at the time of writing grades websites’ progressive enhancement based on their ability to work without JavaScript. Everything, not just JavaScript, should be progressive enhancements.

HTML elements already have progressive enhancement built-in. CSS, JS, and embedded content should be progressively enhanced too. The page should make sense without scripts and styles, alt-text should be available in the absence of embedded media, etc. We shouldn’t put scripting on a pedestal above everything else.

Expand text...

23 June at 19:52 | Open on pleroma.envs.net

Wyatt (🏳️‍⚧️♀?)

@dillo what does "progressive enhancement" mean in this case?
In any case my site gets an A, I actively tested it in IE5, Netsurf, and Dillo while making it.
https://megatokyo.moe/

23 June at 19:53 | Open on tech.lgbt

Simon Forman

@dillo 👍 I like it. With Dillo you can divide the web into three equivalence classes:

1) Works. (defined as, the site loads, the content is accessible and it looks more-or-less like the author intended.) As a rule such sites load lightning fast.

2) Broken but the content can still be read. Usually the site layout is messed up.

3) Broken completely. Typically a blank page, or garbage without visible content.

23 June at 19:57 | Open on mastodon.social

sophiæ disœder :verified_woozy:

@dillo@fosstodon.org the only gripe i have is they're not 88x31 sized so they wouldn't fit in with any of the other badges/buttons on my site :( otherwise they're great! :D

23 June at 20:12 | Open on f.619.hu

Michał :runbsd: :emacs:

@dillo for me the “non essential” functionality is a bit vague. What if it’s js snow in the bg for Christmas? It’s not essential by any means but it will not work

23 June at 20:38 | Open on emacs.ch

Jake in the desert

@dillo love it. This is a really important thing to consider and hardly anyone does.

23 June at 20:44 | Open on c.im

lunchy

@dillo there should be another rating axis that shows if there's harmful functionality that is broken successfully with js turned off

23 June at 20:51 | Open on tilde.zone