78616 2012-02-14 10:03:15 -0800 Consider formulating RenderReplaced as an effect of shadow DOM 2019-10-04 22:13:06 -0700 1 1 1 Unclassified WebKit Layout and Rendering 528+ (Nightly build) Unspecified Unspecified RESOLVED WONTFIX P2 Normal --- 82313 1 dglazkov webcomponents-bugzilla dbates dominicc hayato morrita rniwa shinyak oldest_to_newest 556370 0 dglazkov 2012-02-14 10:03:15 -0800 From discussion on bug 50126, Niwa-san suggested a pretty nifty idea: what if we re-describe all elements that currently rely on RenderReplaced for rendering as elements with a shadow DOM (created by UA), that looks like this--taken from Ryosuke's comment: HTMLCanvasElement -> ShadowRoot -> some-special-element/renderer, inaccessible from ES5 | v fallback contents (accessible from DOM, focus, etc... would just work when shown) This would solve nicely the fallback content issues with focus and possibly allow us to replace RenderReplaced with a better-defined shadow DOM logic. Also, this dovetails pretty well into https://www.w3.org/Bugs/Public/show_bug.cgi?id=15802. 556419 1 rniwa 2012-02-14 11:12:18 -0800 One drawback of this approach is that we'll double or triple the number of nodes for replaced elements depending on how we implement them. So we might want to add some clever memory-saving mechanism along the way.