You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fieldset incorrectly gets set in error when a child input is in error #245
It seems like the fieldset component will set itself in error if one of the child inputs inside it is in error. This is not correct - it should only be in error if the fieldset as a whole is in error.
The result is that the left red error bar extends across the entire fieldset, rather than just the field that is in error.
You could possibly say that this is something to be decided on a question by question basis - but then this shouldn't be the default as it's not how the native components work.
It's not in the docs, but reading the package source, I see you can use <Fieldset disableErrorLine="false"> to explicitly disable this.
Incorrect:
Correct:
There's no example of this in the NHS design system, but it's covered in the GOV.UK design system:
Activity
colinrotherham commentedon Sep 9, 2025
@edwardhorsford @rowellx68 Can you see if I've fixed this in #267?
edwardhorsford commentedon Sep 10, 2025
I can see
disableErrorLineis no longer present.Will there be related changelogs / upgrade notes for these things that have been removed / changed? This alone could be a breaking change.
colinrotherham commentedon Sep 10, 2025
Yeah here's the Upgrading to 6.0 guide from #267
Fieldsets are no longer necessary in the sense that, if a component wants one, it does it itself
edwardhorsford commentedon Sep 10, 2025
I don't see
disableErrorLinebeing mentioned in the guide - should we mention that it's been removed?colinrotherham commentedon Sep 10, 2025
Yeah, for people that forget to remove
<Fieldset>?It's still there on every form component and the
<SingleInputFormGroup><FormGroup>wrappercolinrotherham commentedon Sep 29, 2025
Since every component that uses
<FormGroup>can set/unset its ownerrorwe no longer needdisableErrorLineConfirming it's closed by #267 and the guide has been updated