- From: cynthia <notifications@github.com>
- Date: Tue, 23 Mar 2021 01:42:24 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 23 March 2021 08:42:36 UTC
Hi, apologies for the delayed response - this fell through the cracks (never got a proper milestone update - our bad) and luckily was noticed by @plinss. > Could you please let us know if the above answers address your concerns or not? To be honest, I'm afraid not - but given this: > This is currently blocking spec review & shipping in Chromium as based on the outcome of this discussion it may lead to significant changes in the API structure/code. We also don't think we should block work - the core concerns have been raised long enough ago, but we don't think it was addressed in a timely manner. However, given that there is a deadline and we don't think there is much else for us to do here. That said, we have also noticed that representatives from different implementors have raised [1] [2] similar concerns and we do not think the concerns have been properly addressed. For these reasons, we plan to close this during our plenary. [1] https://github.com/w3c/editing/issues/225#issuecomment-611482377 [2] https://github.com/w3c/editing/issues/225#issuecomment-614917371 -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/507#issuecomment-804723066
Received on Tuesday, 23 March 2021 08:42:36 UTC