kyledrake 1 hour ago

If I was working on web standards, I would focus on trying to make the browser able to do as much as possible without JavaScript. Having to use JS to post a form dynamically for example is extremely overkill and a security problem. If we could avoid it more often, we could use CSP headers and disable it on a lot more security critical sites. If doing accessibility is a problem without JS, well then there's a great thing to get started on fixing.

Just read this article this morning which I think highlights the problem: https://www.newsweek.com/cyber-attack-websites-affected-1272...

I think it's really cool that browsers are VMs that can run Doom now but I really think we need to come back and focus on the basics again: HTML as hand-editable documents you read, more interface components, accessibility tools. Not sure the Gemini protocol (https://en.wikipedia.org/wiki/Gemini_(protocol) will succeed but I understand and loved the spirit of it.

  • bflesch 32 minutes ago

    Now you know why google is incentivized to create a browser

edoceo 2 hours ago

The classes are many and use common names that would conflict with existing style making this tedious to add into existing, but for green field I might give it a try. Maybe your css builder lets me prefix?

metalliqaz 3 hours ago

I really like the idea of minimalism and doing as much as possible without js. I love the look and feel of sites that do what they need without client side programming. Maybe I'm just old fashioned but it seems more permanent, more stable, more content oriented, more useful

  • seki285 2 hours ago

    It's more of a hassle and a lot of the time is a bunch of unintuitive hacks. I hope we see more mainlined APIs for the browser instead

    • adzm 2 hours ago

      Like many things there is a good middle ground. HTML dialog and popover APIs are great, but combining that with javascript helps smooth out the rough edges.

      A good example of this is the toast notification on this site. It is cool that we can pop up a toast using only HTML... but it can't be dismissed by anything other than user interaction.

alwinaugustin 2 hours ago

I most of the time ask agents to create html instead of markdown as it is easy to understand in case of diagrams etc and use tailwind. Will give this a try.

slopinthebag 2 hours ago

doesn’t seem very accessible which is the downside to js-free widgets

  • prafandy 2 hours ago

    Fair point, and I'd really like to know where it fell short for you. What did you try? The weak spot I know of is the tabs: a screen reader hears them as radio buttons, not tabs.

  • dawnerd 2 hours ago

    This is why I gave up doing css only for this kinda stuff a looong time ago. It’s cool you can do it but not so fun when you get lawyers claiming your site isnt accessible.

  • nadinengland 2 hours ago

    What aspect of it isn’t accessible? Would love to know.

    • lopis 20 minutes ago

      For example: a screen-reader-only user doesn't know that the "Selected invoices" banner appeared, together with the download button. You'd need to use certain ARIA labels to inform the screen reader that the dynamic content of the page changed.

etatester 1 hour ago

Cool exercise, but it's a lot of work that nobody is interested in. I know because I used to be a big proponent of "progressive enhancement" but nobody cared.

I guess that now that code is free you can turn it into a skill and hope for the best; but the moment you need more complexity you're going to build Rube Goldberg machines.