Post

Would you, today, choose to use <input type=image> for some reason? If so, why?

2 reposts2 likes

Yeah, used it in another side project to load pictures, scale down to 48x48 pixels, grab the color per pixel, get nearest LEGO compatible color and create a mosaic picture with building instructions. Why?

My thesis was essentially this: no one is using it in new projects and it's entire 1% chrome usage stats will be from historical usage before CSS let you style buttons fully (e.g. gradient backgrounds or even image backgrounds). Now I'm fully prepared to be told I'm wrong it was just my hunch.

Custom as in, better than what a web component would allow you to do? If only we'd get some more pseudo elements to style, that would be a win.

It still sends the coordinates of the image you’ve clicked on as GET parameters. So if you need that for some reason, then why not? 😬

I don't remember the last time I used it. Maybe like 20 years ago 🤔 So, no. Nothing special, and I would expect its usage numbers would show the same.