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.