W3C home > Mailing lists > Public > www-style@w3.org > May 2013

Re: [css3-regions] flow-into: <ident> content-only

From: Alan Stearns <stearns@adobe.com>
Date: Mon, 13 May 2013 15:51:17 -0700
To: Rossen Atanassov <Rossen.Atanassov@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CDB6BACD.2A275%stearns@adobe.com>
On 5/8/13 6:18 PM, "Rossen Atanassov" <Rossen.Atanassov@microsoft.com>

>According to the minutes [1] from 4/24/13 there was a request to me to
>provide a use case for the flow-into: <indet> content-only; proposal.
>Here it is.
>The ability for authors to separate content from views when populating
>templates.  For example, a news aggregator has a set of predefined views
>she uses to display content that is coming from an external source.
>These views are defined
> by one author and the content is defined by another author. The views
>can be composed from various fragment containers.  The containers can be
>predefined or dynamically created (programmatically or declaratively)
>based on the content overflow.  The ability
> to flow the content of a container, removes the requirement of having to
>make all of its individual content pieces to become part of a flow chain.
> For example, an article with the header, sub-headers, and paragraphs
>doesnąt have to carry the container with
> it when it is placed into the view.  The advantage of this model is that
>news aggregators can define name flows to flow content from an external
>source to view on their site. This is more manageable than forcing
>developers to directly insert those elements
> into the view or directly use iframes to display all content on one view.
>* The views represent templates that are created from fragment containers.
>* Authors can define the flow-into and flow-from.  This will allow them
>to associate content to different views.
>* The ability to dynamically create templates based on a
>author-predefined criteria when content overflows (programmatically or
>* The ability to specify that the content-only of an element (and not the
>element itself) can be used to define named flows.
>* The ability to include content from external documents is similar to
>what we do with iframes today.
>Let me know if you have any additional questions.

I think the idea of populating a layout with content from an external
source is quite useful. I also think the content keyword allows for two
additional use cases. The original content container(s) can be used for
fallback scenarios if CSS Regions is not supported, and placing just the
contents of an element into a named flow leaves the box(es) available to
be used as CSS Regions in the named flow's region chain.


Received on Monday, 13 May 2013 22:51:52 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:11 UTC