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
There is a buggy scenario connected with markers, mapper and renaming elements:
Create a marker and map it to a view container element (for example table cell).
Rename that view container element (for example, set/unset table header).
Since the marker range has not changed, it won't be converted. But the renaming will remove the old view container element and insert a new one. This will lead to a situation when view marker representation is lost.
The text was updated successfully, but these errors were encountered:
Other: Introduced automatic marker re-rendering during conversion for markers which view element was unbound. Closes #1780.
BREAKING CHANGE: New parameter introduced in `DowncastDispatcher#convertChanges()`. Now it is `convertChanges( differ, markers, writer )`.
BREAKING CHANGE: Although it was rather impossible to use `DowncastDispatcher` without specifying any conversion API in the constructor, now it is a required parameter.
mlewand
transferred this issue from ckeditor/ckeditor5-engine
Oct 9, 2019
There is a buggy scenario connected with markers, mapper and renaming elements:
Since the marker range has not changed, it won't be converted. But the renaming will remove the old view container element and insert a new one. This will lead to a situation when view marker representation is lost.
The text was updated successfully, but these errors were encountered: