- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Thu, 14 Jun 2012 19:11:46 +0000
- To: Divya Manian <manian@adobe.com>, Tab Atkins Jr. <jackalmage@gmail.com>, Chris Eppstein <chris@eppsteins.net>
- CC: "www-style@w3.org" <www-style@w3.org>
[Divya Manian:] > My point is, we should not go with the solution that is merely palatable > to the CSS WG but we need to find a solution that is as less destructive > in the future and as easy to understand and use *correctly* as possible by > developers. Oh, of course. Tab is only the editor: making him happy is neither necessary nor sufficient...though it kind of helps as long as he's writing the spec (ahem). The feature must make sense for developers at large. But. 1) If you think the current model is going to confuse the hell out of developers 2) If you're having as hard a time convincing the editor of this problem as he has convincing you it's not really an issue, then I think the burden is on you - or Chris, or whomever else is bothered by this - to propose an alternative that addresses your concern. It can only help. Today, I know *what* Tab proposes and *why* he does so. I think I know *why* you don't like it but *what* you'd rather have seems largely left to my imagination at the moment. And I'll honestly admit it's struggling to fill the gap. It's possible I may not be the only one.
Received on Thursday, 14 June 2012 19:12:36 UTC