- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Fri, 01 Jul 2022 12:48:58 +0000
- To: public-css-archive@w3.org
> That's interesting. What are the cases where `<object>` could be a non-replaced element? Items one and three in [this example](http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A%3Cstyle%3E%0Aobject%20%7B%20border%3A%20medium%20solid%20fuchsia%3B%20%7D%0A%3C%2Fstyle%3E%0A%3Cobject%3Eone%3C%2Fobject%3E%0A%3Cobject%20data%3D%22http%3A%2F%2Fwpt.live%2Fcss%2Fsupport%2Fblue-100.png%22%3Etwo%3C%2Fobject%3E%0A%3Cobject%20data%3D%22url-not-found%22%3Ethree%3C%2Fobject%3E). Note that distinguishing items two and three at value computation time is particularly hard, but I think in general it may be difficult to distinguish replaced elements during value computation, just because that's not the sort of information that's expected to be needed during selector matching and value computation. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7435#issuecomment-1172311271 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 1 July 2022 12:49:00 UTC