Re: CSS Regions considered harmful (was: [css-regions] issue 16858 redux)

Is there a plausible alternative to #1 with any kind of serious
thought/support?  This is an entirely serious question, I'm sure it sounds
snarky or accusatory or something - but it is entirely genuine.  I respect
and actually agree with your goals, I just honestly cannot any longer
imagine a solution and I've not seen one which I think doesn't merely trade
a set of fairly well known problems for which we have, for all it's
problems, learned to use pretty effectively for an unknown set which we
can't say those things about (i.e., will people grok/adopt/etc - and then
what are the holes we come across as it spreads out).

I don't want to sound like I have the answers - I don't.  I'm frankly very
glad to be having this discussion - I think it's an important one.




On Wed, Jan 22, 2014 at 1:58 PM, Håkon Wium Lie <howcome@opera.com> wrote:

> Hello Brian,
>
>  > Is your primary case there that Regions is a bad idea entirely - or
> merely
>  > that they should be moved into/defined only in CSS?  I read the piece
>  > twice, but I was unclear on this point...
>
> My primary point is that we should not abuse HTML tags as this is
> harmful to web semantics. That's problems #1 and it should, alone, be
> enough to stop the specification from progressing.
>
> If problem #1 is fixed, we still have problems #2-#5. Those are not
> quite as clear-cut, but my conclusion is that CSS Regions will create
> more problems than they solve for web designers.
>
>    http://alistapart.com/blog/post/css-regions-considered-harmful
>
> Cheers,
>
> -h&kon
>               Håkon Wium Lie                          CTO °þe®ª
> howcome@opera.com                  http://people.opera.com/howcome
>
>
>
>
>
>
>


-- 
Brian Kardell :: @briankardell :: hitchjs.com