- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Wed, 18 Jan 2012 02:31:01 +0000
- To: Ambrose LI <ambrose.li@gmail.com>
- CC: Marat Tanalin | tanalin.com <mtanalin@yandex.ru>, Tab Atkins Jr. <jackalmage@gmail.com>, "www-style@w3.org" <www-style@w3.org>
[Ambrose LI:] > > 2012/1/17 Sylvain Galineau <sylvaing@microsoft.com>: > > So what's the fix? How do you make the failure non-silent? > > > > That's would, I suppose, not be a CSS problem per se, but purely a > browser-specific implementation issue. Perhaps what we need is just making > it non-silent if developer tools are running. Agree it's a UA issue. It's one modern built-in dev tools do report in various ways but it's doesn't really 'pop'. If this restriction does surprise a large number of folks, a more effective way to report it sounds worthwhile.
Received on Wednesday, 18 January 2012 02:31:34 UTC