- From: fantasai <fantasai.lists@inkedblade.net>
- Date: Wed, 24 Feb 2016 21:30:29 -0500
- To: www-style@w3.org
On 02/24/2016 08:30 PM, Xidorn Quan wrote: > On Thu, Feb 25, 2016 at 9:25 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> On Wed, Feb 24, 2016 at 4:52 PM, Xidorn Quan <quanxunzhen@gmail.com> wrote: >>> On Thu, Feb 25, 2016 at 7:56 AM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >>>> On Mon, Feb 22, 2016 at 12:49 AM, Ting-Yu Lin <tlin@mozilla.com> wrote: >>>>> This question was raised in bug 1221416 when implementing <details> and >>>>> <summary> elements in Firefox. >>>>> >>>>> We might need a way to support styling for the disclosure triangle of the >>>>> <details> (or <summary>) element. Currently, webkit supports a non-standard >>>>> pseudo-class summary::-webkit-details-marker as this article said. >>>>> >>>>> Xidorn proposed here that we could add ::marker support for <summary> >>>>> element in pseudo-element spec. >>>>> >>>>> Any ideas? >>>> >>>> I'm happy with Xidorn's idea, and it's already supported by the >>>> Counter Styles spec, which has list-style values specifically defined >>>> for this. >>> >>> Yes, but the question is, do we want to make <summary> a list-item? I >>> don't think it makes sense. Using list-style on <summary> looks weird >>> to me. In the current spec, ::marker is only generated for list-item >>> (and inline-list-item). If we want to extend the range ::marker is >>> applied to, we would probably need a new concept for it? >> >> The concept is "list-item". It's an unfortunate legacy name, but that >> happens sometimes. > > So you are suggesting we make <summary> (or <details>?) to have > "display: list-item" by default, and applies list-style and ::marker > on it, right? I'm fine with this, though it looks a bit weird, but > acceptable and seems to be practical for implementing. This makes sense to me. What do you think is weird, other than the name of the 'list-item' keyword? ~fantasai
Received on Thursday, 25 February 2016 02:30:57 UTC