facebookarchive/draft-js

Out of sync selectionState within decorator strategy

Open

#484 创建于 2016年6月23日

在 GitHub 查看
 (4 评论) (1 反应) (0 负责人)JavaScript (22,554 star) (2,646 fork)batch import
help wantedquestion

描述

It would be nice for developers to be able to get the selectionState within a decorator strategy. When trying to do this with this.state.editorState.getSelection() inside of the decorator, the data seems to be out of sync.

Try creating a decorator with this strategy

strategy: (contentBlock, callback) =>  {
     const editorStateText = this.state.editorState.getCurrentContent().getPlainText();
     const contentBlockText = contentBlock.getText();

     console.log(editorStateText);
     console.log(contentBlockText);

     //...
},

You will notice that contentBlockText will be one character(or keystroke) ahead of editorStateText when typing.

Does getting an up-to-date selectionState within the decorator strategy seem like a good idea?

贡献者指南

技术栈
javascriptreact
领域
frontend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Familiarity with Draft.js decorator strategiesUnderstanding of React stateJavaScript basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
30
研究方向
The issue describes a mismatch between the selectionState obtained inside a decorator strategy and the actual state. Investigate Draft.js source code for decorator strategy implementation, likely in src/component/decorators/. The problem may be that the strategy receives a snapshot of the editorState rather than the current one. A possible fix is to pass the latest editorState or provide a callback. Since the repository is archived, consider forking the project or exploring alternative text editors like Slate or Lexical.