Skip to content
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

[comp:anchor] anchor 组件使用 v-show时组件宽高计算有误 #849

Closed
1 task done
threedayAAAAA opened this issue Apr 15, 2022 · 2 comments · Fixed by #893
Closed
1 task done

[comp:anchor] anchor 组件使用 v-show时组件宽高计算有误 #849

threedayAAAAA opened this issue Apr 15, 2022 · 2 comments · Fixed by #893
Assignees
Labels
bug Something isn't working Comp:Anchor

Comments

@threedayAAAAA
Copy link
Contributor

threedayAAAAA commented Apr 15, 2022

  • I have searched the issues of this repository and believe that this is not a duplicate.

Reproduction link

https://codesandbox.io/s/romantic-black-73r6wm?file=/src/App.vue

Steps to reproduce

见重现连接

What is expected?

  1. anchor 组件使用 v-show时组件宽高计算正常
  2. 使用v-if时位置计算正常

What is actually happening?

  1. anchor 组件使用 v-show时组件宽高计算有误
  2. 使用v-if时只有页面重绘才会计算位置

Environment Info

见重现连接
@idux-bot
Copy link

idux-bot bot commented Apr 15, 2022

Translation of this issue:

[COMP: Anchor] Anchor Components When using V-Show, the component is high.

  • i Have Searched The [https://github.com/iduxfe/idux/issues) of this repository and believe That this is not a duplicate.

reproduction link

https://codesandbox.io/s/romant-black-73r6wm?file=/src/app.Vue

steps to reproduce

See the reproduction connection

What is expected?

Anchor component uses V-Show time components as high computing normally

What is actually happens?

Anchor components are incorrect with the component as high computing when using V-Show

Environment Info

见重现连接

@danranVm
Copy link
Member

@jackson-yyy 同时也看看 v-if 的情况

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Comp:Anchor
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants