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
It's unclear to me from that link what exactly you're trying to do. Do you have a minimal test case using the Demo.html file in the repo? If you're changing the root node for Squire, you need to destroy the old instance and create a new one.
It doesn't happen when not using a web component. So I'll close the issue. There seems to be something going wrong with getting ranges and the undostack from the webcomponent when the element has moved. Using shortcuts does still work interestingly enough.
I do wonder if the possibility to use the shadow DOM would solve this issue. Are you planning on ever supporting this?
When moving the element that the squire editor is bound to, the editor loses part of its functionality.
An example can be found here:
https://github.com/ddorstijn-usoft/squire-editor
This uses lit element but the idea should remain the same.
Pressing the bold button for example after moving generates the following error:
![afbeelding](https://private-user-images.githubusercontent.com/1730282/281397603-54ba5ea0-eab2-4f77-a017-804f78a66ad8.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5ODUwNzIsIm5iZiI6MTczODk4NDc3MiwicGF0aCI6Ii8xNzMwMjgyLzI4MTM5NzYwMy01NGJhNWVhMC1lYWIyLTRmNzctYTAxNy04MDRmNzhhNjZhZDgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOCUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDhUMDMxOTMyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9OTEyNjlhYzk1YjAyYTE3NWNhNzk5M2UwY2Y5ZTFmMjVkMTIxMjQ3YTNlMzBiZWMyMzIyN2ViYzI1NjVlYjFhMCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.7ior7uer8eCa_l1fvzQDR73EjrAtQrKaabjJkuZbPTs)
Also after pressing the undo button the value of the editor will be
undefined
The text was updated successfully, but these errors were encountered: