Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

HTML Can Do That

chrisburnell.com

Post reply on HN
Print view View original

31–40 of 249 posts

Re: HTML Can Do That

#31

Post by bulder »

Gualdrapo wrote: post #18
dematz wrote: post #8

This comment by yurishimo should not be [dead], imo >Just a heads up but datalist is not really a great solution if you need a strong contract. The user can still type whatever they want into the field and there is no fuzzy filtering or typo mitigation. Once you add those requirements, a library that gives you a more fully featured combobox is likely going to make a lot of sense in your project. It is true! HTML can…

I seem to recall there was a proposal to add such thing to s

I definitely remember seeing a post by a Chromium maintainer talking about starting development on a proof of concept implementation and surveying for semantics.

Re: HTML Can Do That

#32

Post by gear54rus »

hollowturtle wrote: post #29

An "HTML Can't Do That" would be hundreds pages long, and at the pace of getting features like dialogs every decade we're limiting ourselfs on any further development and creating serious apps. It wasn't created for apps, it was created for light document formatting. When we will pretend a drawing api we can call directly from webassembly? Outside of web ui frameworks are doing just fine and way better and more perfo…

> When we will pretend a drawing api we can call directly from webassembly?

Hopefully, never. There's enough ad-blocking arms race as it is.

Re: HTML Can Do That

#33

Post by gunalx »

jamescun wrote: post #5

I'm that minutia in your statistics that is still rocking NoScript in 2026, enabling JavaScript on a site-by-site basis, but this is increasingly difficult with the modern web. Hopefully these and others modern HTML features gain adoption, along with realizing perhaps a Single Page Application isn't necessary in most instances. I don't often have to write frontend code, but when I do, there is very little in terms of…

Single page applications are one of the most anoying web patterns i know of. Please just let me have one page for each ting to do so i actually can bookmark it properly.

Re: HTML Can Do That

#36

Post by bellowsgulch »

The older I get, the less I want to use new browser features that have already been somehow possible with existing ones that typically have been around for literal decades.

Adopting them makes a future with multiple browser engines more labor intensive and unlikely as the number of standards targets one is required to support grows and it becomes a game of asking yourself what sites you want your browser to support.

If you don't have a lot of experience in web software, you might think, that's a silly thing to think about, but I think it's that level of maybe exceptional thoughtfulness that has really profound ramifications. If you do have a lot of experience in web software and you think it's silly to think about, you suck.

Re: HTML Can Do That

#37

Post by wild_egg »

hk__2 wrote: post #20

Related to this, I’d love that HTML natively support sortable tables. This is a common need but every single time I have to reimplement it.

You want client side table sorting?

It's really easy to do this with server rendered HTML. Put a link with the sort param in the column headers and be done.

Re: HTML Can Do That

#38

Post by phyzix5761 »

gunalx wrote: post #33
jamescun wrote: post #5

I'm that minutia in your statistics that is still rocking NoScript in 2026, enabling JavaScript on a site-by-site basis, but this is increasingly difficult with the modern web. Hopefully these and others modern HTML features gain adoption, along with realizing perhaps a Single Page Application isn't necessary in most instances. I don't often have to write frontend code, but when I do, there is very little in terms of…

Single page applications are one of the most anoying web patterns i know of. Please just let me have one page for each ting to do so i actually can bookmark it properly.

Once backend and frontend became two separate teams frontend people didn't want to keep asking backend to make logic changes for state, so frontend took things into their own hands. The mistake was making it two separate teams.

Re: HTML Can Do That

#39

Post by dspillett »

seki285 wrote: post #11
jdlshore wrote: post #4

The “hidden until found” feature surprised me. What’s the use case for something like that?

One thing that comes to mind is JS-less image preview, clicking on an image thumbnail reveals the full preview.

Though that wouldn't have a method of closing the full image afterwards, if you have a few thumbnails and want one full to be open at a time (closing when the next is selected).

Re: HTML Can Do That

#40

Post by djoldman »

jamescun wrote: post #5

I'm that minutia in your statistics that is still rocking NoScript in 2026, enabling JavaScript on a site-by-site basis, but this is increasingly difficult with the modern web. Hopefully these and others modern HTML features gain adoption, along with realizing perhaps a Single Page Application isn't necessary in most instances. I don't often have to write frontend code, but when I do, there is very little in terms of…

oh my. Looks like NoScript is way better than what I've been using. Thanks!

https://noscript.net/

Post reply on HN