- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Mon, 28 Oct 2013 15:32:36 -0700
- To: Håkon Wium Lie <howcome@opera.com>
- Cc: François REMY <francois.remy.dev@outlook.com>, Alan Stearns <stearns@adobe.com>, Johannes Wilm <johannes@fiduswriter.org>, www-style list <www-style@w3.org>
On Mon, Oct 28, 2013 at 3:10 PM, Håkon Wium Lie <howcome@opera.com> wrote: > Also sprach Tab Atkins Jr.: > > > > For b), I think the answer is no. And if you disagree, maybe you > > > should consult the HTML WG before proceeding. > > > > As Alan keeps saying over and over again, Regions is totally > > compatible with, and frankly *begs* for, better ways to generate boxes > > in CSS. > > Then we should design that CSS mechanism and not expose regions as > HTML elements. You cut out the rest of what I said, which was a direct response to what you just said: > However, the underlying functionality, the primitive that > we're exposing, doesn't intrinsically care about whether it's filling > a box that originally came from CSS or HTML. They're equivalent at > the level of the primitive, and we shouldn't try to complicate things > further than that *at the level of the primitive*. Doing so will just > mean that authors have to jump through more hoops when they try to do > something outside of what we've imagined. ~TJ
Received on Monday, 28 October 2013 22:33:23 UTC