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

[Bug Report] el-tabs__active-bar width calculation is incorrect #15216

Closed
weeqe opened this issue Apr 23, 2019 · 1 comment · Fixed by #15461
Closed

[Bug Report] el-tabs__active-bar width calculation is incorrect #15216

weeqe opened this issue Apr 23, 2019 · 1 comment · Fixed by #15461
Assignees
Milestone

Comments

@weeqe
Copy link

weeqe commented Apr 23, 2019

Element UI version

2.7.2

OS/Browsers version

win10,chrome 72.0.3626.121

Vue version

2.5.16

Reproduction Link

https://codepen.io/anon/pen/axaodL?&editable=true

Steps to reproduce

定时补偿任务的子菜单el-tabs__active-bar宽度计算不正确,且只有el-tabs的type为border-card或card的时候才会出现

What is Expected?

修改el-tabs__active-bar宽度

What is actually happening?

宽度不一致

@element-bot element-bot changed the title [Bug Report] el-tabs__active-bar宽度计算不正确 [Bug Report] el-tabs__active-bar width calculation is incorrect Apr 23, 2019
@element-bot
Copy link
Member

Translation of this issue:

Element UI version

2.7.2

OS/Browsers version

Win10, chrome 72.0.3626.121

Vue version

2.5.16

Reproduction Link

Https://codepen.io/anon/pen/axaodL?&editable=true

Steps to reproduce

The subtenu el-tabs__active-bar width of the timing compensation task is incorrectly calculated, and only when the type of el-tabs is border-card or card will it appear.

What is Expected?

Modifying el-tabs__active-bar width

What is actually happening?

Width inconsistency

@island205 island205 added this to the 2.9.0 milestone May 8, 2019
@SimonaliaChen SimonaliaChen self-assigned this May 8, 2019
SimonaliaChen pushed a commit to SimonaliaChen/element that referenced this issue May 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants