- From: Botond Ballo via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Jun 2021 02:02:50 +0000
- To: public-css-archive@w3.org
> <fremy> fantasai: one more comment > <fremy> fantasai: it's a bit weird how things happened here > <fremy> fantasai: we are not doing standardization, we are doing documentation > <fremy> fantasai: I don't find this workflow appropriate > <fremy> fantasai: so I agree to do it here, but it's worth nothing I think it is not a good workflow > <fantasai> fantasai: It's too late to make any changes now, it's not exactly accurate to say you're shifting it to the CSSWG for the "standardization" process Hi, I'm one of the Firefox engineers who worked on this feature. For my future reference, could you clarify what, if anything, we should have done differently? Should we have kept the feature disabled by default until the W3C process completes? Should Chrome have done the same? Thanks, and my apologies if we didn't follow the process correctly. -- GitHub Notification of comment by theres-waldo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6339#issuecomment-863698931 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 June 2021 02:03:23 UTC