- From: Brad Kemper <brad.kemper@gmail.com>
- Date: Thu, 9 Jun 2011 10:50:00 -0700
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On Jun 9, 2011, at 9:34 AM, "Tab Atkins Jr." <jackalmage@gmail.com> wrote: > On Wed, Jun 8, 2011 at 6:39 AM, fantasai <fantasai.lists@inkedblade.net> wrote: >> On 06/08/2011 04:28 PM, Tab Atkins Jr. wrote: >>> >>> On Tue, Jun 7, 2011 at 11:55 PM, Brad Kemper<brad.kemper@gmail.com> >>> wrote: >>>> >>>> On Jun 6, 2011, at 11:43 PM, fantasai<fantasai.lists@inkedblade.net> >>>> wrote: >>>> >>>>> I think we should make it clear if/how 'vertical-align' can be used to >>>>> position list markers. >>>> >>>> Supposedly all properties are fair game. >>> >>> Indeed. 'inside' list markers are just inline-block elements, and >> >> Why are they inline-blocks instead of inlines? That does not make >> much sense to me. > > I think I just made the choice fairly arbitrarily. You can't tell the > difference currently, because you can't make a marker that would > line-wrap. This statement surprises me a lot. Why wouldn't it wrap if I had this: ::marker { display: inline-block /* or block or table-cell */; width: 2em; } /* assume spaces in marker text, or else 'word-break: break-all' or that breaking after decimals is part of 'word-break: normal' */ > I don't see too much wrong with making them inlines. They'll still > act properly when positioned with 'outside', so sure. Cool. That is less magic than having 'position' also change the initial 'display' value, right? (floats are magic in that regard).
Received on Thursday, 9 June 2011 17:50:35 UTC