- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 May 2017 00:44:48 +0000
- To: public-css-archive@w3.org
> I totally get that this doesn't make sense for the current level of the spec Thanks for confirming. > I do wonder if this bug is an appropriate place (or if there's a better place) to track the issue long term. Totally personal take on this question: while it does seem that there's a genuine use case to solve here, I think there was enough skepticism in the WG (including from myself) of how it's supposed to work that a mere feature request is unlikely to lead anywhere soon, and that a fleshed out proposal would have better chances either to convince the WG that it's doable, or to explore the problem enough to uncover a different way to solve it. My suggestion would be that you start a draft specification somewhere you control (similarly to WIP proposals from [Tab](https://github.com/tabatkins/specs/blob/gh-pages/README.md) or [myself](https://specs.rivoal.net/)), and keep this group in the loop (either via github or via the www-style@w3.org mailinglist). You could do that in a github issue as well, but I don't find that's a very good place to maintain a specification. This is not an attempt to make you go away, nor a suggestion that you go incubate it somewhere else. The hard part about this proposal is that it needs to work well with the rest of the layout system, so this is the right group to talk to, but you're going to need to be more specific, and a draft spec could be a good way to do that. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1043#issuecomment-300341289 using your GitHub account
Received on Wednesday, 10 May 2017 00:44:54 UTC