Piotrek Koszuliński

> But wait, why we need to access body? I have the impression that floating elements will be simply inside the custom element itself. See my comment above. They cannot...

I did :P Because they won't be rendered if the editor is in an element which has `overflow:hidden` and fixed size (which happens). It's the same case as an editor...

Or maybe I'm wrong... https://jsfiddle.net/pp7z788w/ Strange. Cause I'm pretty sure there were problems with that. Otherwise, why would CKE4 went this way? Maybe it was some old browser. We should...

OK, now it's bad: https://jsfiddle.net/pp7z788w/1/

Heh... let me guess. CKE4 was forced to put floating stuff to the body, because there was no `position:fixed` in IE6? :D If there's no gotcha with the `position:fixed`, then...

> I'm not 100% sure that fixed will be always working fine, but IMO it seems like a good solution. If we're able to easily get the position of some...

> If we go with position:fixed, it will mean constant re–positioning when the web page scrolls because viewport is constant and to follow the content that panel/toolbar is attached to...

Not yet. We haven't researched it so neither we know how hard will it be nor have we seen much interest on that (I guess that this is because it's...

Thanks for the updates! Do you know how stable and consistent is `contentEditable` and `Selection` in shadow DOM and shadydom? My biggest worry now is that investing in researching how...

Apologies for lack of repsonse from our side. We should have been more active :( We'd like to look into this PR. However, without the CLA signed by the author...