Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fieldset support for readonly property #10783

Closed
StfBauer opened this issue Nov 20, 2024 · 2 comments
Closed

fieldset support for readonly property #10783

StfBauer opened this issue Nov 20, 2024 · 2 comments
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest

Comments

@StfBauer
Copy link

What problem are you trying to solve?

When I have multiple fields combined in a field set. I am able to define:

<fieldset id="fieldset-1" disabled="true" />

This will disable all field inside of the <fieldset/>. This means that the fields are somewhat hidden and not enabled to be changed.

When I like to show the field but make them only 'readonly' I have to set the property on all the fields inside the fieldset.

To me this seems to be inconsistent.

What solutions exist today?

The solution is to update the fields one by one individually with 'readonly' property. Works fine but is sometimes not really efficient to make fields readonly.

Alternatively they could be rendered with just using

or elements.

How would you solve it?

To have a consitent form experience I would add the readonly property to fieldset, which then would make the fieldset in its entierly 'readonly'

Anything else?

No thats all and thanks for your feedback in advance.

@StfBauer StfBauer added addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest labels Nov 20, 2024
@annevk
Copy link
Member

annevk commented Nov 22, 2024

This is a duplicate of #10293.

@annevk annevk closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2024
@StfBauer
Copy link
Author

@annevk sorry ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
addition/proposal New features or enhancements needs implementer interest Moving the issue forward requires implementers to express interest
Development

No branches or pull requests

2 participants