From 4869dec9b433d3b7409e86c4dc0f188ec01b779b Mon Sep 17 00:00:00 2001
From: dfedoryshchev <dmitriy.fedoryshchev@gmail.com>
Date: Fri, 1 May 2026 21:28:11 +0100
Subject: [PATCH] docs: clarify register validation rules vs native HTML
 attributes

---
 src/content/docs/useform/register.mdx | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/src/content/docs/useform/register.mdx b/src/content/docs/useform/register.mdx
index 8f18c11b2..ce920a9b6 100644
--- a/src/content/docs/useform/register.mdx
+++ b/src/content/docs/useform/register.mdx
@@ -47,6 +47,12 @@ This is how submitted values will look like:
 
 By selecting the register option, the API table below will get updated.
 
+<Admonition type="note">
+
+These are validation rules, not native HTML attributes. They run based on the form's [`mode`](/docs/useform#mode) and don't block typing. To also forward `required`, `min`, `max`, `minLength`, `maxLength`, and `pattern` as native attributes on the input, set [`progressive`](/docs/useform/form) to `true` on `useForm`.
+
+</Admonition>
+
 <TabGroup buttonLabels={["validation", "validation and error message"]}>
 
 <div style={{ background: 'var(--color-options)', padding: 20 }}>