W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2020

Re: [csswg-drafts] [css-sizing] clarification around Compressible Replaced Elements and min-content size (#5665)

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Wed, 09 Dec 2020 22:40:18 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-742108761-1607553616-sysbot+gh@w3.org>
>  As in, why should this replaced-element exception
> [...]apply[...]
>     * when there is no compat requirement?

FWIW, pushing back on this part: there is actually some amount of webcompat requirement for Chrome's behavior here.  See the list of "see also" webcompat bug reports at https://bugzilla.mozilla.org/show_bug.cgi?id=1585485 -- there are 9 distinct reports there right now, which include quite high-profile sites like [Yahoo](https://github.com/webcompat/web-bugs/issues/47442), [Bing](https://github.com/webcompat/web-bugs/issues/54652), [GitHub](https://webcompat.com/issues/59567)], [NameCheap](https://github.com/webcompat/web-bugs/issues/61254), and [Heineken](https://webcompat.com/issues/40634) (the last of which is at least a big brand if not a big web presence).

That's part of why we're leaning towards switching Firefox to match Chrome's behavior (and the spec, to the extent that I understand it correctly). I suspect if instead Chrome switched to match Firefox, you'd end up needing to roll back the change due to webcompat fallout.

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5665#issuecomment-742108761 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 December 2020 22:40:19 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:23 UTC