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

After the select component is clicked, it will report an error after being destroyed Cannot read property'removeEventListener' of null #3878

Closed
1 task
wcldyx opened this issue Mar 29, 2021 · 6 comments

Comments

@wcldyx
Copy link

wcldyx commented Mar 29, 2021

error

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

Version

2.1.1

Environment

win10, chrome89

Reproduction link

Edit on CodeSandbox

Steps to reproduce

1: 先点开select 选择器
2:然后点 销毁 按钮(销毁组件后会报错)

What is expected?

能正常销毁select 组件

What is actually happening?

select 组件在被销毁后报错:Cannot read property 'removeEventListener' of null


经过反复测试,引起报错的位置在 ant-design-vue/es/vc-virtual-list/ScrollBar.js 里面,beforeUnmount 方法被调用了两次导致错误

@github-actions github-actions bot changed the title select 组件在点开后,被销毁后会报错 Cannot read property 'removeEventListener' of null After the select component is clicked, it will report an error after being destroyed Cannot read property'removeEventListener' of null Mar 29, 2021
@sendya
Copy link
Member

sendya commented Mar 30, 2021

降级到 vue3.0.7,等 vue 修复

@lihxhit
Copy link

lihxhit commented Mar 30, 2021

vue 3.0.9好像还是有这个问题

@sendya
Copy link
Member

sendya commented Mar 30, 2021

vue 3.0.9好像还是有这个问题

就是3.0.9出现的问题

@moetanahy
Copy link

I'm getting this problem as well in 3.0.9. Does anyone have any solutions or know when this might be fixed?

@tangjinzhou
Copy link
Member

update vue to 3.0.10

@github-actions
Copy link

github-actions bot commented Apr 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 Apr 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants