- From: Corné Dorrestijn via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Dec 2022 12:51:41 +0000
- To: public-css-archive@w3.org
I've already created a bug report here: https://bugs.chromium.org/p/chromium/issues/detail?id=1400940 since this discussion was not linked in https://developer.chrome.com/blog/overflow-replaced-elements/ and did not find any other resources at the time. But the current implementation in Chromium results in a difference between the `img` element and a `input` with `type="image"`. After reading through the discussion here, I don't think the input is considered. There could be two situations in the end. One where the input is also using the overflow property. However, this could cause issues since an ink overflow is not enough here (since the user can not interact with the overflowed ink). A second situation is one where input does not use the overflow property, and thus keeps working as before. This however results in different behavior in replaced elements. -- GitHub Notification of comment by cornedor Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7144#issuecomment-1351296930 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 December 2022 12:51:43 UTC