<iframe> elements are documented asThe HTML Inline Frame Element (<iframe>) represents a nested browsing context, effectively embedding another HTML page into the current page.However, most WYSIWYG editors HTML5 frameworks (such as tinymce, Aloha, Maqetta, etc...) are using a lot <iframe> but they intuitively do not need a new nested browsing context... (the canonical example of <iframe> is to show another website, but all the WYSIWYG editors in HTML I heard about are usable on the same website).So why is <iframe> so important in that case? We know that contenteditable is terrible (so is probably not enough for WYSIWYG editors in HTML5).(I guess it is related to event handling & capturing & bubbling, but I don't understand the relationship with <iframe>s)PS. This SO question gives the motivation and the context of my question, and this one explains why contenteditable is disappointing for me.
why are iframe-s so useful in HTML5 WYSIWIG applications?
javascript;html5;dom