Replace fieldsets with divs.

[willnationsdev]

Closes #108. There are now no more mentions of "fieldset" within the codebase except for a TODO in ToggleGroup.svelte.

Note that I had a large number of warnings/errors in my VS Code project, but everything built (and seemed to behave) just fine. May have just misconfigured something on my end, idk.

1. Gave the new <div> elements a "group" role.
2. Identified each element/component supporting disabled and made sure to pass the parent component's state to it since the <fieldset> previously would've affected nested form fields' disabled state automatically.
   • The Input component did not have a disabled property, so I had to add one.

If I missed anything, please feel free to let me know (or just fix w/ a follow-up).

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
svelte-ux	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 4, 2023 3:29am

[what-the-diff]

PR Summary

• Changed container types in Field and TextField components
  The container element type has been changed from <fieldset> to <div> in Field.svelte and TextField.svelte. This might help to make the styles and behaviors more consistent across different browsers.

• Added 'disabled' property to Button component
  A new disabled property has been added to the <Button> element in Field.svelte and TextField.svelte. This will allow users to disable these buttons when required, providing better interaction control in our interface.

• Renamed slot in MenuField component
  The slot "fieldset" has been renamed to "root" in MenuField.svelte. This could improve code readability and clarity.

• Enhanced TextField component with 'disabled' property
  The disabled property has been added to various elements within TextField.svelte. This gives additional control over the interaction with these elements, contributing to a more intuitive user experience.

[techniq]

@willnationsdev Thanks! Now that you mention it, I think disabled was maybe another reason I used fieldset. In some cases, I'll add pointer-events-none on the container to make sure nothing is clickable in the disabled state, but I like passing disabled down in this case, especially since that's how it worked (inherently).

I gave it a run through and everything looked unchanged. Thanks again!