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

Re: [css3-regions] Separating regions markup

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 12 Mar 2013 14:39:40 -0700
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <CD64E93D.1F74A%stearns@adobe.com>
On 2/8/13 1:31 PM, "Alan Stearns" <stearns@adobe.com> wrote:

>On 1/30/13 2:55 PM, "Håkon Wium Lie" <howcome@opera.com> wrote:
>>Bert Bos wrote, on 29 Nov 2012:
>> > > As I mentioned last week, I've edited the sample code in Appendix A
>> > > [1] in CSS Regions to move the regions elements to a separate file
>> > > using custom elements from Web Components [2].
>> > > 
>> > > Bert, Håkon - does this approach satisfy your requirement for
>> > > separating content markup from layout?
>> > 
>> > I think it can work.
>>Certainly, it's much better than having empty elements in HTML files.
>I intend to re-work the example to move the <style> block to the
>x-fancy-layout.html file. I think this is much more straightforward and
>allows for better fallback - if the external file does not load or custom
>elements are not supported, the content flows above the image as if the
>'is' attribute did not exist.

I have made this change to Appendix A and switched all of the example code
in the css3-regions draft to use HTML Templates [1] to separate content
markup from layout. I also added a note (currently note 2) describing this
use and linking to the various web components specs.

Please take a look at the changes. I believe this satisfies the concerns
behind issue 16858 [2] about (a) keeping content separate from layout and
(b) using good practices in spec examples.



[2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=16858
Received on Tuesday, 12 March 2013 21:40:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:27 UTC