fix(VFab): improve positioning & examples #20318
Merged
+198
−212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Original goal was to restore VFab + VSpeedDial example (original in v2 docs) after hearing colleague on Discord saying he does not know the path to migrate
v-speed-dial
withfixed
. Upgrade guide states thatfixed
andabsolute
are combined inposition
, but this is not the case here.There is also a minor problem that traditional usage when
v-speed-dial
wraps element with<template #activator>
makes the menu attach to.v-fab
wrapper element which extends far beyond the visible button. So the only viable usage is to wrapv-speed-dial
insidev-fab
. We should consider explaining it in the Upgrade guide.Notes:
absolute
toapp
causesError: [Vuetify] Could not find injected layout
, and:key="..."
may seem unnecessary, but prevents this issueMarkup: