I disagree. There's a reason the W3C policy is that no spec is stable until there are two independent implementations. Browser devs can make unconscious assumptions that aren't specified. Chrome shouldn't unflag until there are others. Don't want another web components v0 vs v1.
-
-
Replying to @AmeliasBrain @DasSurma and
The WC experience was indeed painful, but it's important to understand why. First, while we weren't able to develop our own engine (pre-fork), we had to try to convince others of the value of components without the ability to _show_. Predictably (in retrospect), then went poorly.
1 reply 0 retweets 2 likes -
Replying to @slightlylate @AmeliasBrain and
Next, we kept asking other browser vendors to join us and help evaluate the designs...and we got a lot of crickets in response. It was only _after_ we shipped V0 and developers showed interest that others came back to the table (culminating in V1).
2 replies 0 retweets 2 likes -
Replying to @slightlylate @AmeliasBrain and
But shipping both was painful; not somethign we want to repeat either! We learned a lot from the experience and have built a whole set of tools and processes to ensure we don't repeat the pain...
1 reply 0 retweets 1 like -
Replying to @slightlylate @AmeliasBrain and
For example, we're committed to getting developer feedback without polluting the ecosystem, so we built the Origin Trials system are are using it heavily: https://www.chromium.org/blink/origin-trials …
1 reply 0 retweets 0 likes -
Replying to @slightlylate @AmeliasBrain and
Except that this thread is about new v0 features you've shipped.
1 reply 0 retweets 1 like -
Replying to @alanstearns @AmeliasBrain and
After running Origin Trials and gathering lots of developer feedback, yes! Leadership requires a leader.
2 replies 0 retweets 1 like -
Replying to @slightlylate @alanstearns and
While that all sounds good, looking through the trials I'm not seeing any Houdini related items. Which leads to my next question based on your premise, which authors have tested this and provided the feedback to deem it safe to ship?https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/completed-trials.md … https://github.com/GoogleChrome/OriginTrials/blob/gh-pages/available-trials.md …
1 reply 0 retweets 4 likes -
Replying to @gregwhitworth @slightlylate and
Yeah, I don't think Houdini features ever used the Origin Trials system, they used the Experimental Features flag. So there were experimental sites, by devs for devs, like https://lab.iamvdo.me/houdini/ , but not production-size tests.
2 replies 0 retweets 0 likes -
Replying to @AmeliasBrain @slightlylate and
yep I'm aware of that one - I was more curious to the feedback aspect since none of them are production versions. At any rate, I'm not too worried about the ones that have currently shipped - but appreciate and respect your hesitancy. The layout API, I have more reservations.
2 replies 0 retweets 2 likes
As a wrinkle we're still working out, shipping to OT requires all the launch bits to flip, which is a ton of work. We had confidence in Custom Paint enough to launch; nearly all the debate on the intent thread was about secure contexts: https://groups.google.com/a/chromium.org/forum/m/#!topic/blink-dev/Jex3idOld48 …
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.