- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jun 2022 14:14:49 +0000
- To: public-css-archive@w3.org
This behaviour for replaced elements is a recent addition to the spec. See discussion [here](https://github.com/w3c/csswg-drafts/issues/7144#issuecomment-1090933632). Since replaced elements need to be clipped by default, we also have UA CSS which depends on the element type to apply the default behaviour (see change [here](https://github.com/tabatkins/html/commit/16943c6e9231a4f5fab89c65ae7ddbe49f40f01b)). > I didn't think computed values could depend on whether something is a replaced element; I don't think that's known at value computation time (e.g., for <object>). That's interesting. What are the cases where <object> could be a non-replaced element? -- GitHub Notification of comment by khushalsagar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7435#issuecomment-1171275555 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 June 2022 14:14:51 UTC