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

append nodes directly #262

Merged
merged 3 commits into from
Nov 29, 2023
Merged

append nodes directly #262

merged 3 commits into from
Nov 29, 2023

Conversation

mbostock
Copy link
Member

Fixes #258. I don’t think we have the same constraints as notebooks where we have to protect against removing an element from the DOM when displaying; here in the CLI, display is a more explicit operation. We want it to work with document fragments, too!

@mbostock mbostock requested review from Fil and cinxmo November 28, 2023 22:46
@mbostock mbostock force-pushed the mbostock/fix-dom-reinsertion branch from 7b1793f to 7526f4b Compare November 29, 2023 01:17
@mbostock mbostock enabled auto-merge (squash) November 29, 2023 02:38
@mbostock mbostock force-pushed the mbostock/fix-dom-reinsertion branch from 7526f4b to 972c9fd Compare November 29, 2023 02:39
@mbostock mbostock merged commit b650996 into main Nov 29, 2023
1 check passed
@mbostock mbostock deleted the mbostock/fix-dom-reinsertion branch November 29, 2023 07:24
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.

Displaying a DOM element that is already displayed elsewhere
2 participants