W3C home > Mailing lists > Public > www-style@w3.org > April 2011

Re: [css3-regions] elements vs. selectors

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 13 Apr 2011 17:36:20 -0700
Message-ID: <BANLkTinPiBt4oGgbhgwBGs6jeDamDvAbtw@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: www-style list <www-style@w3.org>
On Wed, Apr 13, 2011 at 5:30 PM, Alex Mogilevsky <alexmog@microsoft.com> wrote:
>> -----Original Message-----
>> From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
>> Sent: Tuesday, April 12, 2011 10:20 AM
>> To: Alex Mogilevsky
>> Cc: www-style list
>> Subject: Re: [css3-regions] elements vs. selectors
>> We are going to bring to the web another concept of established
>> typographic tradition - linked text boxes. It's a set of containers,
>> possibly of irregular shapes, that text of a story can flow through, and
>> you can follow the story by moving your eyes from one box to another, just
>> like flipping pages.
>> I strongly disagree.  Flowing between regions is dependent on the layout
>> of the page, and the layout of the page can easily change dynamically,
>> based on Media Queries and similar.  HTML can't be generated or changed by
>> anything compatible with MQ.
>> In my opinion, flows should definitely work across pseudo-elements.
>> The fact that they don't have good OM support just means we need to fix
>> that.
> If flow properties are applied through CSS they certainly should applied to generated content. If it can be a table it should be able to be a page container, doesn't sound any harder. But you probably didn't mean to say it should apply to ::first-line too.

Heh, yeah, definitely not ::first-line.  I was referring to the ::slot
pseudo specifically, not pseudo-elements in general.

> What troubles me in motivation for slots is that the *only* real reason for it is that media queries are hard or impossible to use to create or remove elements. But maybe if that is important we need to solve that problem instead? Actual use cases would help...

Well, if you're creating an element via CSS, it doesn't exist in the
real DOM, thus it's basically a pseudo-element, right?  I don't think
we need to invent a new and probably-complex method of altering the
DOM when we already have a mechanism for changing the
DOM-as-CSS-sees-it via pseudo-elements.

At least, I doubt an actual DOM-altering mechanism would be any
simpler than the ::slot mechanism.

Received on Thursday, 14 April 2011 00:37:12 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:45 UTC