Summary: | summary::before renders in wrong position | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Roland Steiner <rolandsteiner> | ||||||
Component: | Layout and Rendering | Assignee: | Web Components Team <webcomponents-bugzilla> | ||||||
Status: | NEW --- | ||||||||
Severity: | Normal | CC: | ahmad.saleem792, ap, bfulgham, dglazkov, dominicc, esprehn, jackalmage, jonlee, morrita, rniwa, shinyak, simon.fraser, webkit-bug-importer, zalan | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | 528+ (Nightly build) | ||||||||
Hardware: | All | ||||||||
OS: | All | ||||||||
Bug Depends on: | |||||||||
Bug Blocks: | 72352, 252223 | ||||||||
Attachments: |
|
Does shadow DOM need a way to specify where the :before/:after content goes? (Something like <content> that can select :before or :after?) In this particular case, our implementation needs to start using CSS3 Lists ::marker semantics for details marker (http://www.w3.org/TR/css3-lists/). This is, of course, is blocked in implementing CSS3 Lists spec. Tree reforming: Unblocking 72352 because 59827 is already blocking it. Created attachment 462105 [details]
All browsers differ from each other
As can be seen from the attached screenshot that all browsers differ from each other. Just want to share updated testing screenshots. Thanks!
Firefox Nightly 107 is now matching Chrome Canary 108 and Safari Technical Preview 155 is just different now. Thanks! |
Created attachment 94749 [details] Test case Generated content with a selector equivalent to "summary::before" renders before the expand/collapse triangle for the parent <details> element. Given that <summary> contains the text that is to be displayed after the triangle, it would probably be more correct to render it directly before that text (i.e., after the triangle) instead. Cf: "li::before" is also rendered directly before the contents of the list items, not before the list item bullet or ordinal.