-
Notifications
You must be signed in to change notification settings - Fork 599
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
fix: move setAttribute calls for proxy elements to connectedCallback #3494
Conversation
026d3c1
to
9421d16
Compare
I have created a branch with |
By setting |
Yes, as I was building your branch I realized that I had started working on that, but it was on your branch. I jumped back to apply some changes and spaced. I think we'll need to set the default appearance differently. |
9421d16
to
da05f11
Compare
@janechu pushed an update. I don't get an error thrown here when testing on your branch. @EisenbergEffect can you take one more look at this when available? One slight change made since you signed off. |
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.
I've built and verified, looks good!
Description
This PR fixes an issue where attributes were defined too early for the custom element, specifically as it relates to form associated elements. This work moves the work to set proxy attributes to the connected callback.
Closes #3456
Motivation & context
Issue type checklist
Is this a breaking change?
Adding or modifying component(s) in
@microsoft/fast-components
checklistProcess & policy checklist