[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@fastkit/vue-disabled-reason@1.1.0

Minor Changes

• #320 4c2343f Thanks @schwarz9791! - - Unmount the reason layers when the component unmounts or when a container is no longer targeted. The layers are rendered imperatively and were never torn down, which leaked the component instances they held.
  • Add a disabled prop. When specified, it takes precedence over the state detected from the DOM, so a wrapped component that already knows its own state (e.g. a readonly input that carries the disabled attribute) can report it accurately. DOM detection remains the fallback when it is not specified.
  • Re-render a reason layer that was removed from its container, e.g. when a text-only child is updated and Vue replaces the container's content.
  • Each reason layer is now rendered into its own display: contents <span> inside the container, so the layer's elements are no longer direct children of the container.
  • A disabled prop defined in the props passed to defineDisabledReasonComponent is replaced by the built-in disabled prop.

@fastkit/vui@1.9.0

Minor Changes

• #320 4c2343f Thanks @schwarz9791! - - VDisabledReason's disabled now tells whether the target is disabled and takes precedence over DOM detection. It replaces the disabled inherited from the menu props, which had no effect. Callers that passed it see the new behavior: false hides the reason even on a disabled target, and true activates the tooltip and the overlay (which catches clicks) on an enabled one.

Patch Changes

• Updated dependencies [4c2343f]:
  • @fastkit/vue-disabled-reason@1.1.0