You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Theoretically we can add custom nodes to the writer field.
The docs are vague about what kind of tags it is possible to add with a node. It seems that it is not possible to add/use the <p> tag with a custom class. The docs give an example about resolving competing marks, but it seems that with a priority below 50 the custom node (with class) is removed, and anything above 50 results in strange behavior where the node gets moved/mashed/added elsewhere once parsed.
Expected behavior
Select a paragraph and apply custom node. Paragraph should now have the class of the custom node.
When page is refreshed the paragraph should still have the class of the custom node, and other nodes should remain the same.
Screenshots
Applying the custom node here, everything seems ok before saving and refreshing the page:
Once the page is saved and refreshed the custom node gets added to all <p> tags if the priority is set above 50:
Description
Theoretically we can add custom nodes to the writer field.
The docs are vague about what kind of tags it is possible to add with a node. It seems that it is not possible to add/use the
<p>
tag with a custom class. The docs give an example about resolving competing marks, but it seems that with a priority below 50 the custom node (with class) is removed, and anything above 50 results in strange behavior where the node gets moved/mashed/added elsewhere once parsed.Expected behavior
Select a paragraph and apply custom node. Paragraph should now have the class of the custom node.
When page is refreshed the paragraph should still have the class of the custom node, and other nodes should remain the same.
Screenshots
Applying the custom node here, everything seems ok before saving and refreshing the page:
Once the page is saved and refreshed the custom node gets added to all
<p>
tags if the priority is set above 50:To reproduce
Create a custom node plugin:
Your setup
4.4.1
Your system (please complete the following information)
The text was updated successfully, but these errors were encountered: