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

Mention 组件受控模式异常 #5788

Closed
skordyr opened this issue Apr 17, 2017 · 1 comment · Fixed by #6004
Closed

Mention 组件受控模式异常 #5788

skordyr opened this issue Apr 17, 2017 · 1 comment · Fixed by #6004
Assignees

Comments

@skordyr
Copy link

skordyr commented Apr 17, 2017

Version

2.9.1

Environment

os: win10 教育版 1703;chome: 57.0.2987.133(正式版本) (64 位)

Reproduction link

http://codepen.io/skordyr/pen/rmVQXQ?editors=001

Steps to reproduce

Mention 组件设置 value 为空字符串的 EditorState 的值,onChange 为空函数(() => {}),此时输入的第二个及其以后的字符会被 Mention 组件渲染。

What is expected?

此时输入不会被 Mention 组件渲染

What is actually happening?

第一个字符输入没被渲染,以后的输入会被输入且无法删除输入的值

RaoHai added a commit to RaoHai/ant-design that referenced this issue May 3, 2017
 #### FEATURES

 * use `ContentState` instead of `EditorState`, selection events won't trigger
   onChange anymore.
 * deprecated `Mention.toEditorState`, instead of `Mention.toContentState`,
 * `Mention.toEditorState` are compatibled, but have a warnning in console.

 #### ISSUES

 * `disabled` and `readOnly` props supported.
 * fixed controlled mode bug.

 * close ant-design#5788
 * close ant-design#5175
 * close #react-component/editor-mention#7
benjycui pushed a commit that referenced this issue May 5, 2017
#### FEATURES

 * use `ContentState` instead of `EditorState`, selection events won't trigger
   onChange anymore.
 * deprecated `Mention.toEditorState`, instead of `Mention.toContentState`,
 * `Mention.toEditorState` are compatibled, but have a warnning in console.

 #### ISSUES

 * `disabled` and `readOnly` props supported.
 * fixed controlled mode bug.

 * close #5788
 * close #5175
 * close #react-component/editor-mention#7
@lock
Copy link

lock bot commented May 3, 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 3, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants