Just now @slightlylate explained the threshold to allow work to move back into @csswg is implementation (= "ready for CR" ?)
-
-
Replying to @svgeesus
: ...also that the goal is to ensure that proposals that get to CSSWG are well-formed, have been iterated on, etc.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
which, I would argue, is certainly the case in this instance
1 reply 0 retweets 0 likes -
Replying to @svgeesus @slightlylate
At the moment, there's a lot of unanswered stuff that has yet to be designed. Not yet iterated/well-formed.
1 reply 0 retweets 0 likes -
Replying to @tabatkins @slightlylate
since you claim there is "a lot" please list three areas that are significantly underspecced, would preclude FPWD
1 reply 0 retweets 0 likes -
Replying to @svgeesus @slightlylate
False assumption - WICG isn't for "things that aren't even FPWD-ready". Ideally things exit incubation at late-WD.
2 replies 0 retweets 2 likes -
Replying to @tabatkins @slightlylate
so, after late-WD it goes to FPWD and triggers a patent exclusion opportunity?
1 reply 0 retweets 0 likes -
Replying to @svgeesus @slightlylate
Yeah, and then achieves patent protection after that period.
1 reply 0 retweets 1 like
: this is what is happening with Payments right now.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.