- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Jun 2020 15:42:32 +0000
- To: public-css-archive@w3.org
I'm a bit concerned about concatenating all the files. I accept that Bikeshed doesn't support multipage specs yet, but I expect it to eventually. And CSS2 is large enough that there's benefit to having both single page and multipage versions. It depends on how Bikeshed will handle multipage specs, whether it will be able to split a single source file to produce a multipage version or it will concatenate multiple sources itself to produce the single page version. And it's likely too soon to know which of those approaches it may require. There's also author and reviewer pain in having a single large source file rather than a number of more manageable files. I'm wondering if, in the meanwhile, it would be better to preserve the individual source files and have a singe additional file that's nothing but a set of includes. cc @tabatkins for any insights into how Bikeshed may wind up supporting multipage specs. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/5196#issuecomment-642751008 using your GitHub account
Received on Thursday, 11 June 2020 15:42:33 UTC