- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Jul 2022 17:40:31 +0000
- To: public-css-archive@w3.org
Ok. I see the point now. We can avoid regressing the behaviour for img elements by applying the rule for replaced elements at used value time as David suggested. So only when the element is rendered as a replaced element it won't create a scroll container (consistent with the behaviour today). But `<object>` would still be affected because the UA CSS rule is marked with !important to keep these elements from generating ink overflow based on the discussion [here](https://github.com/w3c/csswg-drafts/issues/7143#issuecomment-1104143059). -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7435#issuecomment-1177984668 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 July 2022 17:40:33 UTC