-
Notifications
You must be signed in to change notification settings - Fork 41
Ready to resubmit for a TAG review? #75
Comments
Note, we were encouraged to resubmit for review when things moved forward in w3ctag/design-reviews#321 (comment) . |
Looking into this a bit more, I think we need several specification changes first. See the stage 3 blockers label. |
At this point, I think we have strong answers for all of the Stage 3 blockers; formalizing some of the writeups is still in progress, but I'd say it's time to file for another TAG review. Any concerns? |
I think we should come to a conclusion on #22 and then present it to the TAG; that's how they are typically set up to work. |
I've resubmitted this proposal to the TAG. w3ctag/design-reviews#321 (comment) |
We've gotten some interesting review comments at w3ctag/design-reviews#321 . |
We've made changes based on the TAG feedback, summarized at w3ctag/design-reviews#321 (comment), so I'm closing this issue. |
WeakRefs were previously submitted for a TAG review. Since that time, the proposal has advanced significantly, both in its explainer and specification. Is it time for another TAG review, so we can give them a chance to complete the review before anyone feels pressure to ship the feature? cc @tschneidereit @gsathya
The text was updated successfully, but these errors were encountered: