Re: Intent to ship: CSS display:contents

2015-02-04 Thread Mats Palmgren
On 02/04/2015 08:20 PM, cmzieba...@gmail.com wrote: I am trying to set up a CodePen to test this feature: http://codepen.io/WebDevCA/pen/vEeMjx If I understand "display:contents" properly then if it is working the green border around the DIV can't be seen but the contents of the H1 inside that

Re: Intent to ship: CSS display:contents

2015-02-04 Thread Daniel Holbert
Correct. Conceptually, the exists in the style tree (so e.g. your "text-align:center" style gets inherited to the h1, via the style system, and any other inherited properties or "div > * {" style rules would affect the children as well). But the does not exist in the box tree. It's replaced th

Re: Intent to ship: CSS display:contents

2015-02-04 Thread Jonas Sicking
On Mon, Feb 2, 2015 at 1:33 PM, L. David Baron wrote: > On Monday 2015-02-02 11:27 -0800, paul.ir...@gmail.com wrote: >> Hey Mats, the use cases are not obvious to me, but I didn't follow the >> original www-style threads on this so I'm lacking context. (A the spec >> doesn't help either) >> >>

Re: Intent to ship: CSS display:contents

2015-02-04 Thread cmziebarth
I am trying to set up a CodePen to test this feature: http://codepen.io/WebDevCA/pen/vEeMjx If I understand "display:contents" properly then if it is working the green border around the DIV can't be seen but the contents of the H1 inside that DIV can be seen? __

Re: Intent to ship: CSS display:contents

2015-02-02 Thread Mats Palmgren
On 02/02/2015 07:27 PM, paul.ir...@gmail.com wrote: Hey Mats, the use cases are not obvious to me, but I didn't follow the original www-style threads on this so I'm lacking context. (A the spec doesn't help either) Can you help explain why a developer would use `display:contents`? I think it'd

Re: Intent to ship: CSS display:contents

2015-02-02 Thread L. David Baron
On Monday 2015-02-02 11:27 -0800, paul.ir...@gmail.com wrote: > Hey Mats, the use cases are not obvious to me, but I didn't follow the > original www-style threads on this so I'm lacking context. (A the spec > doesn't help either) > > Can you help explain why a developer would use `display:conte

Re: Intent to ship: CSS display:contents

2015-02-02 Thread Tantek Çelik
I'll rephrase Paul Irish's excellent question. Rather than an email to be lost in archives, could you provide a URL to a wiki page where the web designer / developer use-cases for "display:contents" are documented, e.g. one use-case per section? If not, I'm happy to ask the CSSWG myself. Tantek

Re: Intent to ship: CSS display:contents

2015-02-02 Thread paul . irish
Hey Mats, the use cases are not obvious to me, but I didn't follow the original www-style threads on this so I'm lacking context. (A the spec doesn't help either) Can you help explain why a developer would use `display:contents`? I think it'd help to have it described a bit. Thanks! _

Re: Intent to ship: CSS display:contents

2015-02-02 Thread Jet Villegas
CSSWG determined that display:contents covers use cases that CSS Grid subgrid would otherwise cover [1]. We may punt on subgrid now that we've got display:contents in Gecko. Other UAs have voiced support for the same at the May 2014 F2F. --Jet [1] https://lists.w3.org/Archives/Public/www-style/20

Re: Intent to ship: CSS display:contents

2015-02-02 Thread Mats Palmgren
On 02/02/2015 04:11 PM, Boris Zbarsky wrote: On 2/1/15 4:36 PM, Mats Palmgren wrote: CSS display:contents has been enabled by default in v37 and my intent is to ship this feature in v37 on all platforms. Do we have any indication on whether any other UAs are planning to ship this? I'm not aw

Re: Intent to ship: CSS display:contents

2015-02-02 Thread Boris Zbarsky
On 2/1/15 4:36 PM, Mats Palmgren wrote: CSS display:contents has been enabled by default in v37 and my intent is to ship this feature in v37 on all platforms. Do we have any indication on whether any other UAs are planning to ship this? -Boris ___

Intent to ship: CSS display:contents

2015-02-02 Thread Mats Palmgren
CSS display:contents has been enabled by default in v37 and my intent is to ship this feature in v37 on all platforms. It can be disabled by setting the hidden preference layout.css.display-contents.enabled to false. Link to standard: CSS Display Module Level 3 http://dev.w3.org/csswg/css-displa