- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 22:33:28 +0000
- To: public-css-archive@w3.org
I continue to object to the idea that calling the images "images" is somehow confusing. The child elements *are* images, both literally and semantically; the image-focused object-* properties apply to them. I still don't understand what @fantasai was trying to say in her argument against it. Calling it **image** would indeed be confusing and wrong, since it's a container for the images, not an image itself. But "images" is fine; the plural clearly indicates it's a container, and its children are the images being discussed. Ultimately, as you say, this element will be rarely targeted, so its name doesn't matter that much, I just don't want us to deliberately choose a bad name for invalid reasons. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7788#issuecomment-1275353915 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 October 2022 22:33:30 UTC