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

Exposing Fundamental Primitives (was: [css-regions] Named Flows, Elements and Box Generation)

From: Brian Kardell <bkardell@gmail.com>
Date: Mon, 28 Oct 2013 19:46:17 -0400
Message-ID: <CADC=+jeXgUBRHa5xO37bE+VWZbWCSCmQNxXyXiyySiaPe+oA4Q@mail.gmail.com>
To: François REMY <francois.remy.dev@outlook.com>
Cc: Johannes Wilm <johannes@fiduswriter.org>, www-style@w3.org, "Tab Atkins Jr." <jackalmage@gmail.com>, Alan Stearns <stearns@adobe.com>, Hċkon Wium Lie <howcome@opera.com>
Apologies for delayed response to this thread, feel like i helped instigate
some of this discussion via other channels and then didn't show up to
participate when it came up.

Numerous WG members are of the opinion that we need to, as the Extensible
Web Manifesto says, prioritize explaining the magic and exposing the
fundamental primitives in the system.  I won't rehash the rationale for
this, but encourage you to read it for yourself and the plenty of articles
written about it.  I will note though that it explicitly states explains
how this helps us develop better high level apis - that we definitely want
them.

All of this said, what are they?  This requires some archeology and
discussion.  Alan has done a great job explaining how regions provide a
possible part of an answer, but at least a few disagree.  My question is:
is there some alternate answer that would make you happier?  Personally, i
think the named regions work is great, it makes a lot of sense to me, but
maybe there is another explanation someone has?  If so, i would love to
see/participate in the discussion as i really think that only through this
kind of change that allows us to tighten the feedback loop and
experiment/compete high level solutions can we go too much further with css
and hope for it to be palletable/understandable.
Received on Monday, 28 October 2013 23:46:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:03 UTC