- From: François REMY <francois.remy.dev@outlook.com>
- Date: Tue, 28 Jan 2014 00:02:33 +0100
- To: "'Tab Atkins Jr.'" <jackalmage@gmail.com>
- CC: "'www-style list'" <www-style@w3.org>
± De : Tab Atkins Jr. [mailto:jackalmage@gmail.com] ± No one doubts that it's less powerful. It's argued that the power loss is small ± enough, and the reduction in complexity large enough, that it could still be a ± worthwhile move. I know. I just wanted to give an idea of what would be missing. Namely: (1) We couldn’t use the default HTML tags and Web Components (2) We couldn’t put ids or classes on regions (and if we need to style fragments, we would have to specify all the style in one single rule, like if we were limited to inline style in HTML) and (3) no JavaScript way of harnessing the power of fragmentation, meaning we continue the trends of making CSS an obscure black box. At the same time, to get an reasonable level expressivity with "overflow: fragments", an almost identical level of complexity will be required as the most difficult thing to get right in regions, unless proven otherwise, is the fragmentation behavior in non-indentically-sized boxes which would remain necessary.
Received on Monday, 27 January 2014 23:03:06 UTC