89054 2012-06-13 19:43:44 -0700 document.execCommand('Indent') removes Shadow DOM. 2012-06-22 17:34:28 -0700 1 1 1 Unclassified WebKit HTML Editing 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 82697 1 shinyak webkit-unassigned dglazkov dominicc enrica hayato morrita rniwa tasak oldest_to_newest 648711 0 shinyak 2012-06-13 19:43:44 -0700 Repro: <div contenteditable> BEFORE HOST <div id="host">HOST</div> AFTER HOST </div> Shadow DOM for host <span>BEFORE SHADOW<shadow></shadow>AFTER SHADOW</span> When performing document.execCommand('Indent') in BEFORE HOST, the Shadow DOM for host disappears. 648794 1 shinyak 2012-06-13 21:56:07 -0700 This is because node->cloneNode() does not clone Shadow DOM. However, if we clone Shadow DOM always, it might be harmful for existing elements e.g. <input> etc. We should think this more. 648796 2 shinyak 2012-06-13 21:56:35 -0700 See also: CompositeEditCommand::moveParagraphWithClones() 655781 3 shinyak 2012-06-22 14:40:17 -0700 We should discuss how do we clone Shadow DOM (or do not clone Shadow DOM) before fixing this problem. 655871 4 hayato 2012-06-22 16:00:50 -0700 I think editing command should treat pure DOM structures in general. That means if we clone some nodes in editing, it is okay that everything that can not be serialized into text is not cloned. like event listeners or attached Shadow DOM created by user. So I vote for WONTFIX for now. (In reply to comment #3) > We should discuss how do we clone Shadow DOM (or do not clone Shadow DOM) before fixing this problem. 655951 5 shinyak 2012-06-22 17:26:59 -0700 (In reply to comment #4) > I think editing command should treat pure DOM structures in general. > That means if we clone some nodes in editing, it is okay that everything that can not be serialized into text is not cloned. like event listeners or attached Shadow DOM created by user. > > So I vote for WONTFIX for now. > > (In reply to comment #3) > > We should discuss how do we clone Shadow DOM (or do not clone Shadow DOM) before fixing this problem. Yeah, I agree with you. Something weid things like disappearing Shadow DOM or Event Listeners etc. cannot be evitable for now. We should discuss this more, but we have higher priority things than this. I vote for closing as LATER. 655958 6 rniwa 2012-06-22 17:34:28 -0700 This is same thing as shadow DOM being lost in copy & paste. Won't fix.