Andrew Boyd

@Archetipo95 I have a fix for this that will be released in `1.6.1`

Something like `closest()` is probably the most common naming convention for that behaviour.

We'll still be fixing this for the theme, but if you use the new `popover` prop that was released today in FormKit Pro `0.120.0` then you should no longer have...

This has been fixed — run `npx formkit@latest theme` in your project to update your theme.

@sashamilenkovic is correct — we do not automatically import the standalone `FormKitIcon` component. You will need to either register it globally or import it into the components that use it....

That’s a great point. I somehow missed that this was in the context of a Nuxt app. I would expect that component to also be available as an automatic import....

@garbit Thank you for the thorough report. Looking into this I stripped down the playground to it's most basic reproduction. The following steps "fix" the issue: - Removing the `beforeStepChange`...

Closing — please feel free to re-open if there's an argument against the current behavior.

In the next release, the `for` attributes will be removed from the `label` elements for these inputs as there are no corresponding inputs associated with the `label`. Advice online seems...