The original title is "Objects should shut the fuck up". I don't like unnecessary cursing either, but it is emphasizing his frustration in this case and cursing objects, not people.
Renaming the title is just losing information for no reason.
This implementation is unnecessary complicated. For the step update, you can use Out Of Band update: https://htmx.org/attributes/hx-swap-oob/ which works in a way that you can send multiple HTML fragments which can be anywhere on the page and HTML swaps them out. Good for notifications, step update, breadcrumb update, menu highlight, etc...
I usually solve the second problem by simply saving the state of the individual input fields, you only need a user session.
Depending your use-case, you might need to be transactional, but you can still do this saving everything as "partial" and close the "transaction" (whatever it might mean in the given context) at the last step. Much-much simpler than sending form data over and over.
> For the step update, you can use Out Of Band update
I did mention using OOB, but I preferred swapping the entire Stepper because the logic on the backend was just a little bit cleaner, and the Stepper didn't include anything else anyways.
> I usually solve the second problem by simply saving the state of the individual input fields, you only need a user session.
I believe this is exactly what I did in the article, no?
I'm experiencing something similar with Firefox. I have a canvas fingerprint-blocker extension that's going haywire and preventing the full page from rendering.
Are you using some form of canvas fingerprinting, either intentionally or unintentionally (through third-party scripts)?