Provide a new form component to simplify form authoring

[danroth27]

When I tried to implement a logout form, this is what I ended up with:

<form method="post" @onsubmit="Logout" @formname="logout">
    <button type="submit">Logout</button>
    <AntiforgeryToken />
</form>

It didn't make sense to use EditForm for this form because EditForm requires a model or an edit context, which I don't really need.

A couple of observations:

• I had to explicitly specify a form name, which is now required for all forms
• I had to manually add antiforgery support

In Razor Pages the form tag helper handles these concerns for you:

<form asp-page="/Identity/Account/Logout" method="post" >
    <button type="submit">Logout</button>
</form>

Should we provide a new framework component that makes authoring these sorts of forms easier?

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[Bartmax]

Also I find impossible to submit a normal (not enhanced) form post now (for example for cookie auth) in RC1.

[danroth27]

Also I find impossible to submit a normal (not enhanced) form post now (for example for cookie auth) in RC1.

Hi @Bartmax. This sounds like something we should investigate. Could you please open a new issue for this with details on how to reproduce the issue?

[Bartmax]

Hey @danroth27, the issue of not able to do a normal (full page) post in a form on RC1 (without turning the whole thing off) is already taken care on RC2 with a way to individually opt-in/opt-out of enhance navigation on forms/links.

I still do find that solution problematic, so I did open an issue for that here #50887

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.