- From: Amelia Bellamy-Royds <notifications@github.com>
- Date: Thu, 23 May 2019 20:10:09 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Friday, 24 May 2019 03:10:31 UTC
@othermaciej Apologies for confusing matters. I hadn't realized that the decision to merge the pull request was despite lack of consensus. So — while it specifies many previously unspecified non-interoperably implemented details — saying it “addresses inconsistencies” may have been premature. Regardless, for the purpose of this TAG review, I thought it was important to record that there were multiple implementations, and some had shipped as non-experimental APIs, and that the shipped implementations weren't fully interoperable, since none of that was in the original request for review. But your contributions about lack of consensus, & the underlying architectural issues behind it, are equally important for the discussion, so thanks for the clarifications. -- 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/353#issuecomment-495456636
Received on Friday, 24 May 2019 03:10:31 UTC