- From: Domenic Denicola via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Sep 2018 14:02:42 +0000
- To: public-css-archive@w3.org
Part of the disconnect here, I believe, is that we (the Chrome team) have been doing a lot of developer and partner outreach around these features. We've heard a few times that the feature is much less useful without part forwarding. We've also heard from people who prefer string reflection, and the proposal for map reflection was seen as unnecessary and would not be used. But we haven't done a good job getting those partners to speak up to the CSSWG on this repository. We can work on that, which can help steer the discussion. If nothing else, several of them will be attending TPAC. If necessary, we can also break off features which need more data into a separate incubation repository and spec. Then we can work on shipping them and gathering in-the-field data on their usefulness. Or not---if it turns out early feedback was wrong, and people don't use those features or need them changed, then we can revise the incubating features before anyone else invests energy in shipping. -- GitHub Notification of comment by domenic Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2368#issuecomment-425104613 using your GitHub account
Received on Thursday, 27 September 2018 14:02:47 UTC