See also T350768: Disable submit button on form submission to prevent duplicate POST requests.

@Madalina @TAdeleye_WMF should we do this task as part of the MTP?

Tagging also Design-System-Team, as I don't think a "pending" state exists for the Button component (https://doc.wikimedia.org/codex/latest/components/demos/button.html), and I think it would make sense to define one. (Or, Codex could otherwise provide a standard way for dialogs to indicate form submission is in progress, as we had in OOUI.)

I'd leave it out of the MTP and add it to our next iteration.

In T350769#9315493, @kostajh wrote:

See also T350768: Disable submit button on form submission to prevent duplicate POST requests.

@Madalina @TAdeleye_WMF should we do this task as part of the MTP?

Tagging also Design-System-Team, as I don't think a "pending" state exists for the Button component (https://doc.wikimedia.org/codex/latest/components/demos/button.html), and I think it would make sense to define one. (Or, Codex could otherwise provide a standard way for dialogs to indicate form submission is in progress, as we had in OOUI.)

I believe we previously discussed this as a team and concluded that applying the disabled interactive state would be the recommendation until a more explicit loading state is considered for buttons, so for now I'd go for what's suggested in T350768.

In the meantime I've filed T350801: Progress elements: Explore alternatives to Button loading states to further discuss explicit guidelines from DST on "pending" button states.