FormData & submitter[formaction] about xhr

[annevk]

Alright, let's reopen this to see if more people hit this or if we find it to be a common library pattern or Stack Overflow question. Thanks!

[annevk]

It seems this would be rather magical as https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#constructing-the-form-data-set has an early return for an empty form. I guess we would have to pretend that the form contains the submitter in this case.

Perhaps you could elaborate on when this kind of thing has come up?

[Lcfvs]

Sorry, my bad... Honestly, I just discovered that requirement: "Does nothing if there is no form owner."

Then a submitter can't be standalone, invalidating my question.

I'm self-asking why that required dependency but don't want to annoy you longer with that.

Thanks anyway.

[annevk]

You're not annoying me! Just curious. I think the dependency is there because we get the fields from the form and then the submitter identifies the field that is the submitter. As I suggested above we could potentially invert some of that, but would need a compelling use case and some signal of web developer demand.

[Lcfvs]

Ok, ok :)

In fact, actually, the idea behind to use them, as standalone, is to replace some anchors by some button[formaction]...

• to avoid any risks related to the page preview feature of some browsers (AFAIK like planned for Chrome)
• to have a "dynamic" variable sent to the server, based on the attributes (name & value), without to have something to manage it, even in GET/POST and/or in AJAX or not

And, really, I'm not convinced about the need of an extra form, trailing somewhere in the page to be able to send one of these buttons requests... moreover since it requires an id, "polluting" the globalThis for that... where these buttons can have anything we need to perform the requests, alone.

[Lcfvs]

Thanks a lot for that shared curiosity :)