The default bug view has changed. See this FAQ.

CSS Template Layout Module

UNCONFIRMED
Unassigned

Status

()

Core
CSS Parsing and Computation
UNCONFIRMED
5 years ago
5 months ago

People

(Reporter: Zéfling, Unassigned)

Tracking

(Depends on: 2 bugs, {css3})

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [mozfr-community], URL)

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 5.2; WOW64; rv:11.0a1) Gecko/20111209 Firefox/11.0a1
Build ID: 20111209031218

Steps to reproduce:

I would like to propose the inclusion of plans to develop a draft standard for firefox CSS Template Layout Module.
(Reporter)

Updated

5 years ago
Keywords: css3
OS: Windows Server 2003 → All
Hardware: x86_64 → All
I believe the CSS WG has no plans to go forward on this draft.  See the thread starting http://lists.w3.org/Archives/Public/www-style/2011Dec/0296.html
(Reporter)

Comment 2

5 years ago
For me it is different, much easier to read, powerful and more compact than Grid Layout.
That's great, but no one is planning to write the spec or implement it...
(Reporter)

Comment 4

5 years ago
Template Layout has been moved to CSS4.
Depends on: 616605, 674802
Summary: CSS Template Layout Module → CSS Grid Template Layout Module
(Reporter)

Updated

2 years ago
Summary: CSS Grid Template Layout Module → CSS Template Layout Module
(Reporter)

Updated

10 months ago
Whiteboard: [mozfr-community]

Comment 5

5 months ago
(In reply to Zéfling from comment #4)
> Template Layout has been moved to CSS4.

There is no such thing as "CSS4" (https://drafts.csswg.org/css-2015/#css-levels). The last published version of this spec has a "Working Group Note" status effectively meaning that the work on it has been stopped (https://www.w3.org/2015/Process-20150901/#tr-end). The latest Editor's draft has the following remark:
> This document currently serves as a repository for ideas around using templates
> for laying out elements, regions or pages; and for various alternative layout models.
> It is expected to be updated, but it is not expected to become a W3C Recommendation
> in this form. Instead, ideas may migrate to other modules of CSS.

Maybe it's time to close this issue as not relevant anymore and open the new one when those other modules incorporate these ideas?
You need to log in before you can comment on or make changes to this bug.