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

表格组件横向滚动纵向不滚动时nzBordered无效(v10-v11) #6254

Closed
232650413 opened this issue Dec 24, 2020 · 1 comment · Fixed by #6367
Closed

表格组件横向滚动纵向不滚动时nzBordered无效(v10-v11) #6254

232650413 opened this issue Dec 24, 2020 · 1 comment · Fixed by #6367
Assignees

Comments

@232650413
Copy link

232650413 commented Dec 24, 2020

Reproduction link

https://qfp4an--run.stackblitz.io

Steps to reproduce

按文档示例,取消Y滚动,仅留X (横向)滚动(nzScroll)时nzBordered无效。

What is expected?

滚动不影响nzBordered

What is actually happening?

取消Y滚动,仅留X (横向)滚动(nzScroll)时nzBordered无效。

Environment Info
ng-zorro-antd 11.0.0
Browser Chrome

版本10到11问题

@zorro-bot
Copy link

zorro-bot bot commented Dec 24, 2020

Translation of this issue:

The table component is rolling longitudinally without scrolling NZBORDERED invalid

reproduction link

[https://stackblitz.com/edit/qfp4an--r??file=src/app/app.component.ts](https://stackblitz.com/Edit/qfp4an--Run?file=src/app/ app.component.ts)

steps to reproduce

Press the document example, cancel the Y scrolling, only x (lateral) scroll (nzscroll) is invalid.

What is expected?

Scrolling does not affect NZBORDERED

What is actually happens?

Cancel Y rolling, only x (lateral) scroll (nzscroll) is invalid.

ENVIRONMENT INFO
Ng-Zorro-ANTD 11.0.0
Browser Chrome

Version 10 to 11 issues

@232650413 232650413 changed the title 表格组件横向滚动纵向不滚动时nzBordered无效 表格组件横向滚动纵向不滚动时nzBordered无效(v10-v11) Dec 24, 2020
vthinkxie pushed a commit to vthinkxie/ng-zorro-antd that referenced this issue Jan 22, 2021
hsuanxyz pushed a commit that referenced this issue Jan 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants