- From: Bogdan Brinza <bbrinza@microsoft.com>
- Date: Wed, 12 Nov 2014 20:34:54 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: "www-style@w3.org" <www-style@w3.org>, Florian Rivoal <florian@rivoal.net>
> It is indeed intended that 'content' work on arbitrary elements. That said, > the Glass website is using it in an absolutely terrible way - it's not doing some > sort of CSS-based *replacement* of content (to upgrade text to an image, > for example), it's just, for no reason that I can ascertain, providing the > element with content through CSS rather than with an <img>. That's bizarre > and stupid; there's no reason to have an empty <a>. So it sounds there are two specific follow-ups here: 1) As we'd still like to fix the site - it would be nice to outreach to Google Glass site and suggest fixing this pattern. Tab, can you help with this, or should we go with normal Microsoft outreach process (either would work)? 2) we assume the spec intent is correct per WG comments and I'll add supporting this to IE backlog.
Received on Wednesday, 12 November 2014 20:35:24 UTC