- From: Xidorn Quan via GitHub <sysbot+gh@w3.org>
- Date: Sun, 21 Jul 2019 02:37:52 +0000
- To: public-css-archive@w3.org
I think it would be the best to be provided by the image itself (mechanism to be explored, e.g. maybe new attribute in svg, and new table in png). I'm not sure how much it makes sense to have a CSS property controlling that. This is a piece of information bound to the content rather than its style, so the value would need to be specified for each specific image, and it's probably not very likely that you can just apply a value to some random content that you cannot control otherwise. For images that doesn't have such metadata but you can manually provide it, you may either update itself or wrap it inside for example an SVG. If we do want to provide some control in the page, given its closer binding to the content, it's probably better being an attribute than a CSS property. Oh, and maybe `<canvas>` and `<video>` etc. would want something alike. -- GitHub Notification of comment by upsuper Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4116#issuecomment-513514255 using your GitHub account
Received on Sunday, 21 July 2019 02:37:54 UTC