Re: [csswg-drafts] [css-grid] Percentage tracks and indefinite sizes

The Working Group just discussed `[css-grid] Percentage tracks and indefinite sizes`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-grid] Percentage tracks and indefinite sizes<br>
&lt;dael> github:  https://github.com/w3c/csswg-drafts/issues/1921#issuecomment-347993853<br>
&lt;dael> astearns: We decided on a change, but it was pointed out impl have interop.<br>
&lt;dael> fantasai: We discussed that at tpac. We re-resolved to do the thing impl don't do. THis is the are you sure you meant the thing.<br>
&lt;dael> florian: We took impl into account when we decided, yes?<br>
&lt;dael> fantasai: We did.<br>
&lt;dael> TabAtkins: We just want to be able to mark WG is cool with this.<br>
&lt;dael> astearns: I'm looking at tpac discussion and I see Rossen_ said this is fine, not a big deal.<br>
&lt;dael> TabAtkins: He jsut didn't want to do it alone b/c it's a breaking change.<br>
&lt;dael> Rossen_: That's true. That's still my point. I'm still okay as long as others do the change as well.<br>
&lt;dael> Rossen_: We're still cool. Others?<br>
&lt;dael> astearns: webkit or gecko?<br>
&lt;dael> dbaron: It's a question for Mats or dholbert<br>
&lt;dael> astearns: dholbert deferred to Mats<br>
&lt;dael> astearns: Given we have two impl willing to make the change and no obj from the others, shall we reaffirm we want this change?<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> dbaron: Who will change first?<br>
&lt;dael> dbaron: If no one will do that we shouldn't do it.<br>
&lt;dael> fantasai: Rossen_ it looks like webkit and blink will follow if you lead.<br>
&lt;fantasai> mrego said “We're not planing to change Blink/WebKit implementations until other browsers do it”<br>
&lt;dael> Rossen_: I won't do it the same way we tried with control characters. I will allow the market leader to lead and we will happily follow. The change is straight forward, but I don't want to introduce interop change.<br>
&lt;dael> Rossen_: For technical decision I'm fine. For scheduling and who when, we won't be first.<br>
&lt;dael> fantasai: Rego said they won't change until other broswers do it.  Igalia folks are good about following up so I don't think it'll get lost. But it will require MS to go first or at least say it's impla ndwill release on a date as long as WB and blink will also trigger.<br>
&lt;dael> Rossen_: How about we table scheduling discussion. If it's as easy for Rego and Igalia as it is for us, let's stop the discussion and we'll discuss timing. As far as spec decision is concerned we'll ship first as long as there are assurances others will follow.<br>
&lt;dael> rego: We checked how many chases will go through this. We first want to gather data on how many websites will break with this change.<br>
&lt;dael> Rossen_: You want us to change to see breakage?<br>
&lt;dael> rego: No, we added a use counter in chromium to gather data. So we want to wait to gather some data before doing anything.<br>
&lt;dael> Rossen_: Sounds good. Let us know that data and what it shows.<br>
&lt;dael> rego: Sure.<br>
&lt;dael> astearns: So anything more on this issue?<br>
&lt;dael> Rossen_: Is take away everyone is still okay pending some data collection from Igalia folks?<br>
&lt;rego> astearns, good summary :-)<br>
&lt;dael> astearns: Yes, pending data collection, impl complexity, and timing of all engines getting change done.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1921#issuecomment-349823979 using your GitHub account

Received on Thursday, 7 December 2017 00:45:42 UTC