- From: Manuel Rego Casasnovas via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 Feb 2019 20:13:39 +0000
- To: public-css-archive@w3.org
> > rego: but it would enable firefox to match both the spec and chrome, because in Chrome we don't follow the spec because it's both faster and easier not to follow it > > Wow, really?!?! That's a pretty lousy attitude coming from a CSSWG member who ought to acknowledge that it's the W3C specs that are the standard that we **all** should implement. I guess the rest of us should just reverse-engineer Chrome now instead of reading the specs, huh? Sorry this was wrong minuted, so let me clarify what I said. I said that Chromium and WebKit are not following the spec, we're only doing 1 pass to compute intrinsic size (and not two 1 under min-content and another under max-content); and that Firefox is doing two passes and following the spec. I also explained that we're not following the spec because we haven't found many cases broken due to this and it's also better to avoid doing the two layouts (we know it's wrong but this part of the implementation comes from old times and we never changed it). Then I also said that if we go with the change suggested here, Firefox won't need to do two passes and that was all. I never wanted to meant that specs should follow what Chromium does at all. Sorry for any misunderstanding. -- GitHub Notification of comment by mrego Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3646#issuecomment-468012898 using your GitHub account
Received on Wednesday, 27 February 2019 20:13:40 UTC