-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
feat(web-components): Use ElementInternals for Radio and RadioGroup components #31783
Conversation
📊 Bundle size report✅ No changes found |
change/@fluentui-web-components-43e80800-54d6-4c42-85f9-c04e6746bd00.json
Outdated
Show resolved
Hide resolved
da4b780
to
492772d
Compare
Support for radio groups in a toolbar will need to come at a later time when a toolbar component is added via #26717 |
dcc4b33
to
f142afa
Compare
5948663
to
e004311
Compare
e004311
to
f7731a0
Compare
f7731a0
to
5024cc9
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work. Such a big update and clear you put a lot of time into. I had a couple questions but there's anything in particular that's blocking me or can't be addressed later in a follow up.
5024cc9
to
6d0bb90
Compare
Previous Behavior
Currently, form-associated custom elements use the
FormAssociated
class mixin. This mixin is heavy and duplicative, being copied wholesale for every component which utilizes it. WhileFormAssociated
includes minimal support forElementInternals
, the implementation isn't fully baked.New Behavior
<fluent-radio>
and<fluent-radio-group>
to useElementInternals
<fluent-field>
,<fluent-checkbox>
, and<fluent-switch>
Related Issue(s)
ElementInternals
#31400