How to destroy the editor instance and how to add the id attribute in span of mention dropdown ?
Here is the js
Here is the code for add anchor tag with attribute Id.
I don't have idea from where I have to call this function if i follow the documentation then it shows error on plugins.
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
As for the destroy, check the method in this article.
What do you mean by span? Your writer creates an a:
As for the destroy, check the method in this article.
What do you mean by span? Your writer creates an
a:
I will replace it with span.
The point is from where I have to call this method If I follow the article it shows error on plugins.
Here
And what is the error?
And what is the error?
The error you can show in image,If I remove the line No 6 from editor's code all works well except mentioncustomization function.I have need to call the MentionCustomization function.
But what is the error in the IDE in line 6?
No error is showing in IDE that's why the editor is not enable. the error is showing on browser only that I shared with you already.
I see that the editor is showing an error on line 6 (red underline). Is there any tooltip there?
I see that the editor is showing an error on line 6 (red underline). Is there any tooltip there?
There is no tooltip.
@Witoso Is there anyone who can help me better.
I would love to help but TBH your IDE shows an error on this line, and you're not reporting what the error is. From what I can tell either the Mention package is not installed or you're importing it in the wrong way.
As I discussed there is no error on IDE the error is on the browser. and I have custom build editor where I select the mention plugin at the time of creation. mention plugin working well until I follow the 3rd line of documentation (plugins line).
There has been no activity on this issue for the past year. We've marked it as stale and will close it in 30 days. We understand it may still be relevant, so if you're interested in the solution, leave a comment or reaction under this issue.
We've closed your issue due to inactivity. We understand that the issue may still be relevant. If so, feel free to open a new one (and link this issue to it).
