Bug: body.getCharacterCount() Returns 1 Instead of 0 After Entering and Deleting Multiple Spaces #9828
Comments
|
Hi @Cho-SeongJu. I'm unable to replicate your issue. Typing two spaces and deleting them, then requesting the character count returns zero. See example. Can you replicate your issue in our fiddle? |
|
I am currently using the following versions.
and example codes import { Editor } from '@tinymce/tinymce-react';
import type { TinyMCEEditor } from 'tinymce';
const handleEditorValueChange = (value: string, editor: TinyMCEEditor) => {
const wordCount = editor.plugins.wordcount;
console.log(wordCount.body.getCharacterCount());
}
<Editor
onEditorChange={handleEditorValueChange}
/>2024-08-16.4.17.05.movIs there a need for version upgrades? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
📝 Provide detailed reproduction steps (if any)
Please provide the steps to reproduce and if possible a minimal demo of the problem via fiddle.tiny.cloud or similar.
Hello. First, I want to mention that I am using the tiny editor effectively before submitting a bug report.
I am using the
wordCount.body.getCharacterCount()method fromconst wordCount = editor.plugins.wordcountto check the character count of the editor. There is a bug where the count does not become 0 when the spacebar is pressed twice and then deleted. I would appreciate it if you could resolve this bug.✔️ Expected result
What is the expected result of the above steps?
2024-08-16.3.23.09.mov
const wordCount = editor.plugins.wordCount; console.log(wordCount.body.getCharacterCount()) // expected result : 0❌ Actual result
What is the actual result of the above steps?
However, when checking with console.log(), it shows 1 instead of 0.
console.log(wordCount.body.getCharacterCount()) // Actual result : 1❓ Possible solution
If you have ideas, you can list them here. Otherwise, you can delete this section.
📃 Other details
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
The text was updated successfully, but these errors were encountered: