[bug?] Both setting the content behavior and content in the tree causes what seems like two DOMElement contents on a single node.
Open
- Dominant language
- JavaScript
- Stars
- 394
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
Example: https://api-beta.famo.us/codemanager/v1/containers/c3283546-9d8b-4c6d-a3c0-dd8c68fae9b4/share
Inspect element on one of those "spinners" and you'll see they contain more than one `famous-dom-element-content` DIV elements.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.