61766 2011-05-31 00:17:01 -0700 details::before/after rendered incorrectly 2024-11-23 11:18:53 -0800 1 1 1 Unclassified WebKit Layout and Rendering 528+ (Nightly build) All All RESOLVED DUPLICATE 157323 P2 Normal --- 72352 252223 1 rolandsteiner webcomponents-bugzilla dglazkov dominicc esprehn igor.oliveira jonlee morrita ntim rniwa shinyak oldest_to_newest 412477 0 rolandsteiner 2011-05-31 00:17:01 -0700 This is similar to bug 61426 (see there for a test case) Generated content from a details::before selector render before any summary or other details-content. Per the CSS spec, content generated with a :before rule should be rendered as if it was the first child of the parent element. For <details> this means that the generated content should become part of the non-<summary> content of the <details> element (and thus hidden if the <details> element is collapsed). Similarly for details::after - this should also become part of the non-summary content (as if the last child) and thus hidden if the element is collapsed (currently it is rendered always). 514941 1 morrita 2011-12-05 00:02:08 -0800 Tree reforming: Unblocking 72352 because 59827 is already blocking it. 848562 2 esprehn 2013-03-06 00:36:08 -0800 The generated content doesn't display at all in this test anymore. Something is bad here because it will show if you create a shadow root manually on an element. Something weird is going on with <details> 848566 3 esprehn 2013-03-06 00:41:56 -0800 (In reply to comment #2) > The generated content doesn't display at all in this test anymore. Something is bad here because it will show if you create a shadow root manually on an element. > > Something weird is going on with <details> This is because of the logic in HTMLDetailsElement::childShouldCreateRenderer. It's unfortunate that the ShadowRoot things in WebCore side step the usual mechanisms that JS developers would use because we end up with behavior you can't explain with the Shadow DOM/HTML Components specs. I think we should fix Shadow DOM to perform distribution on generated content so <content select=":before"> works and then explain <input>'s weirdness with webkit having a <content select=":before"> in there. 2077293 4 ntim 2024-11-23 11:18:53 -0800 Fixed by bug 157323 *** This bug has been marked as a duplicate of bug 157323 ***