Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mention web components, support for the shadow DOM root node on the f… #45

Closed
wants to merge 1 commit into from

Conversation

jonsutherland
Copy link

…ront page. Because it's awesome shit.

Marijn feel free to ignore this or edit the description but I thought this needs more attention. I've noticed you requested assistance on the website, I'll go and check the details in that thread now.

However today after adding custom element support (with shadow DOM) to my code I figured this feature needs a big mention

@marijnh
Copy link
Member

marijnh commented Dec 3, 2016

I am not quite sure what you are referring to here. Just that the editor doesn't break entirely when used in a shadow DOM? I'd consider that kind of baseline functionality, and we're not even there yet on Safari (though that's more of a Safari bug and not really something we can help, see ProseMirror/prosemirror#476).

@jonsutherland
Copy link
Author

Yeah I just got a little excited, HTML import, template, custom elements all seemed to jive when I put pm inside my own component. So when you added support for the shadow root I figured that was something to advertise. But yeah I didn't see anything break using chrome of course. I haven't tested safari. My bad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants