- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Oct 2019 21:24:20 +0000
- To: public-css-archive@w3.org
Pushing a test case through everything would be fine, so long as all the stakeholders in the various systems are on board and available to deal with repercussions. Personally I have higher priority things to work on than chasing this on the draft server at the moment. Especially when the work-around is so trivial. Bear in mind, we're not just necessarily talking about one or two programs, but potential OS and file system issues across multiple versions of multiple OSes, as well as a long-tail of "who's going to get bit by this down the road just because they tried to download a spec and whatever tool didn't encode the filenames properly". Just seems like a lot of work for very little reward here. Also, this isn't a "we'll have to live with it forever" thing, it's more of a question of "is this worth dealing with right now?" cost vs benefit thing. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/4403#issuecomment-540206576 using your GitHub account
Received on Wednesday, 9 October 2019 21:24:21 UTC