Jira issue
What behavior were you expecting?
After marking the text, it should be possible to undo the marker. The marked result shouldn’t be saved.
What actually happened?
Markers are breaking the HTML of the content. The markings can’t be undone and the corrupted HTML will be saved, or a user needs to cancel all modificiations and start over.
This behavior has been confirmed in Shopify. We need to check whether it also applies to WordPress.
How can we reproduce the current behavior?
From this thread: A merchant reach out to us last week saying the following: We've been using your Yoast for Shopify app and we noticed that any time we use the keyword density tool, it can add additional text to the url that causes a broken 404 link -https://www.tileclub.com/products/copper-look-<yoastmark class="yoast-text-mark">picket</yoastmark>-peel-and-stick-<yoastmark class="yoast-text-mark">tile</yoastmark>
If available: what are the tips for fixing the problem or possible solutions?
Basically, we should re-apply the existing PR and this bug-fixing PR, but make sure that the issue that led to the revert does not resurface.
Jira issue
What behavior were you expecting?
After marking the text, it should be possible to undo the marker. The marked result shouldn’t be saved.
What actually happened?
Markers are breaking the HTML of the content. The markings can’t be undone and the corrupted HTML will be saved, or a user needs to cancel all modificiations and start over.
This behavior has been confirmed in Shopify. We need to check whether it also applies to WordPress.
How can we reproduce the current behavior?
From this thread: A merchant reach out to us last week saying the following: We've been using your Yoast for Shopify app and we noticed that any time we use the keyword density tool, it can add additional text to the url that causes a broken 404 link -https://www.tileclub.com/products/copper-look-<yoastmark class="yoast-text-mark">picket</yoastmark>-peel-and-stick-<yoastmark class="yoast-text-mark">tile</yoastmark>
If available: what are the tips for fixing the problem or possible solutions?
Basically, we should re-apply the existing PR and this bug-fixing PR, but make sure that the issue that led to the revert does not resurface.