- From: Ambrose LI <ambrose.li@gmail.com>
- Date: Tue, 17 Jan 2012 18:06:46 -0500
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "Marat Tanalin | tanalin.com" <mtanalin@yandex.ru>, www-style@w3.org
2012/1/17 Tab Atkins Jr. <jackalmage@gmail.com>: > On Tue, Jan 17, 2012 at 2:54 PM, Ambrose LI <ambrose.li@gmail.com> wrote: >> >> If we cared “only about the web” then we can throw a whole bunch of >> W3C initiatives out of the window. As it is, CSS is now caring about >> things that even some professional typesetting systems are unable to >> currently do. > > Personally, I agree - we *should* throw out a whole bunch of W3C initiatives. > > That's irrelevant to my point, though - CSS, specifically, is designed > around the needs of the web. (We do take on some responsibility for > print publishing via epub, Antenna House, Prince, etc., but we've made > decisions against them in favor of the web before.) So two separate things here: 1. Is the current need serving the “needs of the web”? - Technically, maybe (are concurrent downloads always good. I’d say No) - Practically, probably not (the current rule is confusing and leads to errors, though you argue otherwise) (Note: I’m not advocating changing the behaviour. I’m just pointing out that the current behaviour is*making the language more complicated, not less.) 2. Are non-web applications irrelevant for CSS? Personally I’d say NO. Intranet is extremely important, especially when often HTML+CSS is the most natural way to solve a problem. CSS needing to serve print needs, IMHO, directly results from Intranet use needs. -- cheers, -ambrose
Received on Tuesday, 17 January 2012 23:07:17 UTC