-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Open
Labels
internalExternal contributions not acceptedExternal contributions not acceptedissue: feature requestDescribes a new feature and why it should be addedDescribes a new feature and why it should be added
Description
So I'm trying to put blockly in a webcomponent, and I'm getting Uncaught Error: container is not in current document
. Looking at the source code, this appears to be a deliberate line in Blockly.inject()
that checks to make sure you're not using shadow-dom.
// Verify that the container is in document.
if (!goog.dom.contains(document, container)) {
throw 'Error: container is not in current document.';
}
what's the reason for this? is there some principled reason we shouldn't be using blockly in a webcomponent?
gocarlos, crummy, justinfagnani, philipplentzen and garvjeet11
Metadata
Metadata
Assignees
Labels
internalExternal contributions not acceptedExternal contributions not acceptedissue: feature requestDescribes a new feature and why it should be addedDescribes a new feature and why it should be added