Skip to content

Fix for non-required controls becoming required - #30

Merged
lk316 merged 3 commits into
masterfrom
fix-for-non-required-controls-becoming-required
Aug 3, 2026
Merged

Fix for non-required controls becoming required#30
lk316 merged 3 commits into
masterfrom
fix-for-non-required-controls-becoming-required

Conversation

@lk316

@lk316 lk316 commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@Slashek
Slashek requested a review from z-x August 3, 2026 10:29
Comment on lines +94 to +103
/*
The required marker belongs to the field group that holds the required control.
`:has()` is unbounded on its own - `.pos-form :has([required])` is matched by
every ancestor of a required control, not just its group, so any wrapper holding
at least one required control (a `.pos-card` around a set of fieldsets, for
instance) marked every label inside it: optional fields, and fields whose control
is never required at all, such as an upload area. Matching the fieldset keeps the
marker on the group it describes, which is the documented behaviour - labels
placed in a fieldset that has a required input.
*/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not commit Claude's explanations probably.

@lk316
lk316 merged commit a74d5ed into master Aug 3, 2026
3 checks passed
@lk316
lk316 deleted the fix-for-non-required-controls-becoming-required branch August 3, 2026 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants