feat: add shadow dom support, fixes #321 #479
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using angular-editor under a shadow dom encapsulated component, it was throwing errors as it tried to find some elements by their id's using the global document api:
![angular_editor_error](https://user-images.githubusercontent.com/624503/182083670-a8e9d827-d748-4c0f-9ba4-641fe14aae48.png)
This pull request tries to solve it by changing the way we access those elements using Angular's ElementRef instead of document.
It also adds a new page on the angular-editor-app project to showcase the use of angular-editor under a shadow dom encapsulated component.
Test are passing:
![angular_editor_tests](https://user-images.githubusercontent.com/624503/182083850-c576c444-97b4-49f6-9b61-bc16c2458639.png)