Famous/engine

[bug?] Moving a Node to another parent Node causes DOMElement refresh (visible blink).

Open

#472 创建于 2015年8月17日

在 GitHub 查看
 (5 评论) (0 反应) (0 负责人)JavaScript (1,750 star) (262 fork)batch import
help wanted

描述

When we move a child Node to another parent Node, the child Node's DOMElement's HTMLElement will be destroyed and a new one will be generated.

This forces us to reappend elements of other frameworks (f.e. a React component container) to the new HTMLElement of the DOMElement once it's ready.

The process of re-attaching a React component's HTMLElement container causes a visual blink as in this video: <placeholder for video>

The blink is janky. It'd be nice if a DOMElement's HTMLElement was re-used.

cc @alexanderGugel @michaelobriena

贡献者指南

技术栈
javascript
领域
frontend
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
4
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
3-5 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
needs investigation
前置要求
JavaScriptDOM basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
15
研究方向
Investigate how the engine handles node reparenting, likely in the DOMElement module. Check if there's a method to reuse HTMLElements when a node is moved. Look at the source code for node movement logic and any existing tests. Review the comments on the issue for any additional context or attempted fixes.