Re:We keep reinventing CSS, but styling was never the problem
by skydhash on Wednesday August 13, 2025 @06:34AM
(#44886745)
You can have interactivity within a single form, whithout having a whole app code humming in the background. And with the drag and drop example, I often see designers missing the obvious accessibility issue where the user can’t use a mouse.
[ Parent
| on HN ]
Re:We keep reinventing CSS, but styling was never the problem
by pyrale on Wednesday August 13, 2025 @07:40AM
(#44887233)
So you’d need to select a sale, enter a change form, select a new date and validate the change. As opposed to moving the item on your planning.
Accessibility issue is a good point, but the accessible way doesn’t need to be the only way.
Re:We keep reinventing CSS, but styling was never the problem
by skydhash on Wednesday August 13, 2025 @10:32AM
(#44888981)
> So you’d need to select a sale, enter a change form, select a new date and validate the change. As opposed to moving the item on your planning.
That's pre-javascript workflow. You can have your DnD without making your app an SPA. And why not have the DnD and the more complete change form?
Re:We keep reinventing CSS, but styling was never the problem
by pyrale on Wednesday August 13, 2025 @10:53AM
(#44889252)
You're mixing two things here: having an app with more than just CRUD interactions, and making that app an SPA.
My point was giving an example of an app that's a bit more featured than just some forms in a CRUD interface, not that you can only do that with a SPA.
> And why not have the DnD and the more complete change form?
It was, in fact, what we did.