Blazor InputX component use outside of an EditContext/Form

[guardrex]

Input{X} components are covered by the Forms and validation topic with a central focus on using them with an edit context (EditContext/EditForm) pre-7.0. We already have one Input{X} component in use outside of an edit context (InputFile). The rest should be useful outside of an edit context for 7.0 or later ...

• Ideally we'd like to support the input controls existing outside an editcontext.

  per Steve at Throw informative exception when Input Controls are not surrounded by EditForm aspnetcore#27804 (comment).

• Mackinnon furthered things (across the board?) with ...

  Blazor input component support when EditContext is not supplied
  Blazor input component support when EditContext is not supplied aspnetcore#35640

  ... with the caveat on styling ...

  Validation styling won't be applied to input components without an EditContext.

UPDATE (8/16): I'm going to make a significant UID/title/page change here: Since these are for use in and outside of forms, I think we should angle coverage from 'forms validation' to 'forms and input components.' Input components are due their proper respect for use outside of forms. The topic doesn't require radical changes, but the title, UID, and page (forms-validation.md, /forms-validation) should change to better reflect the new world for using these components out in open Razor component markup. I'll include the necessary textual and cross-link updates around the repo to pull this off. IMO, future generations will thank us! 😄

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: eef47457-c8cf-74a4-b884-c1fe5c2ef52d
• Version Independent ID: 09a02d10-2834-467d-d8c2-3fd19ceb3863
• Content: ASP.NET Core Blazor forms and validation
• Content Source: aspnetcore/blazor/forms-validation.md
• Product: aspnet-core
• Technology: aspnetcore-blazor
• GitHub Login: @guardrex
• Microsoft Alias: riande