Skip to content

fix(VAppBar): use actual DOM params #21756

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

OlTrenin
Copy link

Description

fixes #21754

Markup:

const { layoutItemStyles } = useLayoutItem({
      id: props.name,
      order: computed(() => parseInt(props.order, 10)),
      position: toRef(() => props.location),
      layoutSize: height,
      elementSize: height, // This tells layout system to use actual DOM measurements
      active: isActive,
      absolute: toRef(() => props.absolute),
    })

@MajesticPotatoe MajesticPotatoe added T: bug Functionality that does not work as intended/expected C: VAppBar labels Jul 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C: VAppBar T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug Report][3.8.9] VMain computes the wrong --v-layout-top when VAppBar density is compact or comfortable and extensionHeight is 0
2 participants