Bug 61426

Summary: summary::before renders in wrong position
Product: WebKit Reporter: Roland Steiner <rolandsteiner>
Component: Layout and RenderingAssignee: Web Components Team <webcomponents-bugzilla>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, dglazkov, dominicc, esprehn, jackalmage, jonlee, morrita, ntim, 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:
Description Flags
Test case
none
All browsers differ from each other none

Roland Steiner
Reported 2011-05-25 00:53:15 PDT
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.
Attachments
Test case (517 bytes, text/html)
2011-05-25 00:53 PDT, Roland Steiner 		no flags
Details
All browsers differ from each other (622.76 KB, image/png)
2022-09-02 14:00 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Dominic Cooney
Comment 1 2011-05-25 01:23:21 PDT
Does shadow DOM need a way to specify where the :before/:after content goes? (Something like <content> that can select :before or :after?)
Dimitri Glazkov (Google)
Comment 2 2011-05-25 08:27:42 PDT
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.
Hajime Morrita
Comment 3 2011-12-05 00:01:10 PST
Tree reforming: Unblocking 72352 because 59827 is already blocking it.
Ahmad Saleem
Comment 4 2022-09-02 14:00:53 PDT
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!
Radar WebKit Bug Importer
Comment 5 2022-09-02 15:15:15 PDT
<rdar://problem/99506326>
Ahmad Saleem
Comment 6 2022-10-13 07:39:19 PDT
Firefox Nightly 107 is now matching Chrome Canary 108 and Safari Technical Preview 155 is just different now. Thanks!
Tim Nguyen (:ntim)
Comment 7 2024-11-23 11:17:47 PST
Fixed by bug 157323 *** This bug has been marked as a duplicate of bug 157323 ***
Note You need to log in before you can comment on or make changes to this bug.