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

transfer 搜索时 不能正确显示搜索结果 #5631

Closed
wangtao0101 opened this issue Apr 5, 2017 · 6 comments
Closed

transfer 搜索时 不能正确显示搜索结果 #5631

wangtao0101 opened this issue Apr 5, 2017 · 6 comments

Comments

@wangtao0101
Copy link
Contributor

Version

2.9.0

Environment

codepen环境

Reproduction link

http://codepen.io/yuecjnadt/pen/dvLRPm?editors=0010

Steps to reproduce

搜索222时,搜索出一个结果但是不显示

What is expected?

显示content222

What is actually happening?

空的显示框


定位后发现是react-lazy-load的问题
https://github.com/loktar00/react-lazy-load/blob/master/src/utils/inViewport.js#L30 这行代码在搜索时 定位到的element还未重新渲染(还是未搜索时的dom节点)

@benjycui
Copy link
Contributor

benjycui commented Apr 5, 2017

Try Transfer[lazy=false]

It will be better to write your issue/comment in English, so more people can understand you. And this means that more people can help you or benefit from your issue/comment. See: #4897

@benjycui
Copy link
Contributor

benjycui commented Apr 5, 2017

@afc163 I think that we can just remove Transfer[lazy] in antd@3.0, it is usless and buggy.

And we should try #3789 to improve performance.

@wangtao0101
Copy link
Contributor Author

@benjycui I try lazy=false,but it will cause performance problem.

@benjycui
Copy link
Contributor

benjycui commented Apr 5, 2017

Oops....

@afc163
Copy link
Member

afc163 commented Apr 9, 2017

Let's try to fix this first.

@afc163 afc163 self-assigned this May 2, 2017
@afc163 afc163 closed this as completed in ac660d9 May 2, 2017
@lock
Copy link

lock bot commented May 2, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked as resolved and limited conversation to collaborators May 2, 2018
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

3 participants