W3C home > Mailing lists > Public > public-css-archive@w3.org > February 2017

Re: [csswg-drafts] [css-grid] Regarding the 'subgrid' feature

From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
Date: Fri, 03 Feb 2017 03:36:14 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-277156518-1486092973-sysbot+gh@w3.org>
> The feedback on Subgrid from implementers (specifically, from 
Igalia) was what prompted the restriction you are objecting to.

Right, I'm well aware of that.  My impression though, is that their 
conclusions were **not** based on actually trying to implement it.

I think you need to separate "an implementer gives feedback based on 
his/her opinion" vs "an implementer wrote code that tried to implement
 what the spec says and ran into unforeseen problems".  The latter 
category is of course what should count as "evidence based on 
implementation experience".  The former is of course valuable, but the
 latter must be taken much more seriously.

> Again, we did the best we could processing feedback on subgrid...

Yes, and I appreciate that.  But that doesn't mean subgrid is ready to
 be enshrined with CR status.  Unlike the rest of the Grid spec, which
 is now implemented (for the most part) in two major browsers, the 
spec for subgrid has not been battle-tested like that and it's better 
for everyone if it remains in draft status, as I argued in the OP.

Subgrid is both an important feature (we should try hard to get it 
right) and also a rather complex feature (it's unlikely that we'll get
 it right before starting to actually implement it).  I see no 
benefits at all to freezing the feature in its current form before we 
have actual implementation feedback.


-- 
GitHub Notification of comment by MatsPalmgren
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/958#issuecomment-277156518 
using your GitHub account
Received on Friday, 3 February 2017 03:36:54 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:28 UTC