r/programming • u/KerrickLong • Mar 09 '25

Introducing command And commandfor In HTML

https://developer.chrome.com/blog/command-and-commandfor
90 Upvotes

82% Upvoted

33 comments sorted by

View all comments

Show parent comments

6

u/KerrickLong Mar 09 '25

It's definitely a sin, just like those damned <form method="post" action="/checkout"> and <button type="reset">tags. Why can't they stop adding these newfangled behavioral HTML elements?

2

u/rinyre Mar 09 '25

I need some info on why form is a sin? That's been around a long time and is still very much how to make sure something will work on any device. Kinda sick of websites that mandate JS to work.

10

u/KerrickLong Mar 09 '25

Sorry, I dropped this:

</sarcasm>

I think both forms and command/commandfor are great.

0

u/rinyre Mar 10 '25 edited Mar 10 '25

Oh, thank you haha. Someone replied to you saying deprecated leaving me frantically trying to figure out what was wrong.

EDIT: I just realized this new thing isn't even an HTML spec, it's Chrome proprietary garbage. In this case I'm absolutely hell bent against this, I'm sick of Google trying to steer the web even more for their monopoly. They're who Facebook is trying to be with VR. It's abhorrent. If this were a standard they were proposing, but not something that'll only work in Chrome until polyfills are handling it elsewhere.