I would recommend that we ship support for column-span before we unprefix 
column. Shipping only part of a specification like this is risky for interop 
and web compat. Let's get all of it working behind a prefix, and then unprefix 
it all at once. 

(And fix the bugs asap. I've got a bug demo page at: 

On Thursday, October 13, 2016 at 1:28:00 AM UTC-4, Mike Taylor wrote:
> On 10/7/16 5:07 PM, neerjapanch...@gmail.com wrote:
> > Note that we do not yet support the "column-span" property -- that's 
> > covered here:
> > https://bugzilla.mozilla.org/show_bug.cgi?id=616436
> So what's the plan for column-span, exactly?
> We just got a report[1] that the CSSWG site[2] is busted (lol?) because 
> now we understand unprefixed multicol CSS but don't support column-span: 
> all.
> I'm slightly concerned that other sites serving unprefixed multicol CSS 
> will assume column-span support (though admittedly I don't know the 
> history of multicol support, nor how common they co-occur).
> [1] https://github.com/webcompat/web-bugs/issues/3429
> [2] https://www.w3.org/Style/CSS/current-work
> -- 
> Mike Taylor
> Web Compat, Mozilla
dev-platform mailing list

Reply via email to