Context Navigation

Changes between Initial Version and Version 1 of Ticket #14239, comment 15

-                      initial
+                      v1
 Anyway, whether browsers support the experimental custom elements or not isn't really relevant for this report.
 CKEditor supports it: One can define a tag to be allowed, regardless of whether that tag is part of html or not. And that actually works; the tag is not removed upon submit, the tag is properly converted into a widget upon load, etc.
+CKEditor supports it (at least partially): One can define a tag to be allowed, regardless of whether that tag is part of html or not. And that actually works; the tag is not removed upon submit, the tag is properly converted into a widget upon load, etc.
 But when you switch to html-view, those additional elements appear. They were not in the dom-tree prior to that switch. Whether you think my specific use case is a bad idea, adding those elements should not happen should it?
 That sounds like a bug to me.
+But it may be partially a duplicate of #10340 as the content of my tag is empty and could be converted to &nbsp; prior to being converted/moved to a <p>-tag. But the additional <p>'s should still not appear.