tabs最后一项出现了下拉选项

[wustack]

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

Version

4.1.0

Environment

node:v16.20.2； vue/cli:v5.0.8； ant-design-vue:v4.1.2； 电脑系统:windows； 显示器尺寸:1920*1080

Reproduction link

https://github.com/vueComponent/ant-design-vue/tree/main/components/tabs/

Steps to reproduce

1.创建一个新的vue3项目
2.将下方package.json代码复制到package.json文件中 （npm install）
3.将下方App.vue代码复制到App.vue文件中 (npm run serve)
4.在windows电脑中打开任何一种浏览器，在1920*1080的显示器中访问该测试项目，最后一个tab会出现下拉选项
注：代码已尽可能干净

What is expected?

优化显示下拉选项的判断条件

What is actually happening?

在以上步骤下，最后一个tab会出现下拉选项

---

附1：App.vue代码

<template>
  <div class="box">
    <a-tabs>
      <a-tab-pane key="1" tab="6·6嗯嗯嗯嗯"></a-tab-pane>
      <a-tab-pane key="2" tab="6·6嗯嗯嗯嗯"></a-tab-pane>
      <a-tab-pane key="3" tab="6·6嗯嗯嗯嗯"></a-tab-pane>
    </a-tabs>
  </div>
</template>

<script setup></script>

<style scoped>
:deep(.ant-tabs) .ant-tabs-tab {
  font-size: 22px;
}
:deep(.ant-tabs) .ant-tabs-nav-list {
  justify-content: space-between;
  flex: 1;
}
</style>




附2：package.json代码

{
"name": "tab-demo",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint"
},
"dependencies": {
"ant-design-vue": "^4.1.2",
"core-js": "^3.8.3",
"vue": "^3.2.13"
},
"devDependencies": {
"@babel/core": "^7.12.16",
"@babel/eslint-parser": "^7.12.16",
"@vue/cli-plugin-babel": "~5.0.0",
"@vue/cli-plugin-eslint": "~5.0.0",
"@vue/cli-service": "~5.0.0",
"eslint": "^7.32.0",
"eslint-plugin-vue": "^8.0.3"
},
"eslintConfig": {
"root": true,
"env": {
"node": true
},
"extends": [
"plugin:vue/vue3-essential",
"eslint:recommended"
],
"parserOptions": {
"parser": "@babel/eslint-parser"
},
"rules": {}
},
"browserslist": [
"> 1%",
"last 2 versions",
"not dead",
"not ie 11"
]
}







        

<!-- generated by issue-helper. DO NOT REMOVE -->

[wustack]

问题截图

[github-actions]

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.