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

Alert 组件自定义 icon 后,图标错位不对齐(官网的例子也是如此) #3712

Closed
1 task done
zhenzhenChange opened this issue Feb 25, 2021 · 4 comments · Fixed by #3714
Closed
1 task done
Assignees

Comments

@zhenzhenChange
Copy link

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

Version

  • ant-design-vue v2.0.0
  • @ant-design/icons-vue v6.0.1

Environment

Win10 x64、Google Chrome 88.0.4324.182、Vue 3.0.4

Reproduction link

https://2x.antdv.com/components/alert-cn

Steps to reproduce

自定义 icon 错误偏移

errorCode
error


默认 icon 正常对齐

successCode
success

What is expected?

图标居中,与 message 对齐在同一水平线

What is actually happening?

向下偏移

这是官网的例子:

off

@ajuner ajuner self-assigned this Feb 25, 2021
@ajuner ajuner added the bug label Feb 25, 2021
@ajuner
Copy link
Member

ajuner commented Feb 25, 2021

下个版本修复~

@zhenzhenChange
Copy link
Author

zhenzhenChange commented Feb 25, 2021

另外有两点顺带提一下

https://2x.antdv.com/components/overview-cn

  • 新文档里,没有 Tag 标签组件的导航菜单(需要搜索才能找到)
  • 新文档里,每个组件页面最右边的的 API 锚点导航点了也不生效,不会跳转到 API 锚点处

@zhenzhenChange
Copy link
Author

另外有两点顺带提一下

https://2x.antdv.com/components/overview-cn

  • 新文档里,没有 Tag 标签组件的导航菜单(需要搜索才能找到)
  • 新文档里,每个组件页面最右边的的 API 锚点导航点了也不生效,不会跳转到 API 锚点处

这两个问题均已修复,感谢各位的辛勤付出!

@github-actions
Copy link

github-actions bot commented Mar 1, 2022

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants