-
-
Ill try to reframe my question! I'm super aware of the ongoing activities to solve these similar problems. Original question: was there not enough customer ask in between now and 5 years ago, to warrant designing aforementioned API's? This is curiosity about process too.
1 reply 0 retweets 2 likes -
Replying to @TheLarkInn @domenic and
You might phrase this question as an email to your peers over in
@MSEdgeDev who are working with us and the broader community to move designs forward. Doing features via standards is hard, slow, and (apparently) thankless work.3 replies 1 retweet 25 likes -
Replying to @slightlylate @TheLarkInn and
Great to hear that you are all teaming up to get this done. The real questions are: 1: Is there a single person responsible to drive this? If not, can that be fixed? 2: What can be done to accelerate it? What roadblocks can be removed?
1 reply 0 retweets 1 like -
Replying to @chofter @slightlylate and
Things like this are never done by one person. That said,
@flackrw is driving engineering. I’m the Chrome PM. On the Microsoft side there are a bunch of great engineers and@gregwhitworth PMing. It’s a really hard problem because anything we ship *has to* work for frameworks.2 replies 0 retweets 11 likes -
Replying to @stubbornella @chofter and
We’re really lucky that
@brian_d_vaughn has been helping us a ton. His input was great for the prototype@fergal_whatever and@rakinazata built.1 reply 0 retweets 5 likes -
Replying to @stubbornella @chofter and
I can’t speak for everyone, but for me the component needs to be VERY high quality. This is why we started with display locking (so it can be fast and searchable).
@chrishtr’s team has been working on that and we’d *love* feedback from folks with time to try it.1 reply 0 retweets 4 likes -
Replying to @stubbornella @chofter and
Definitely, there are a lot of aspects to get right bringing a component like this to the web. We need to get the performance, ergonomics, accessibility, and delivery model right. We have a prototype but we're still trying to answer a lot of open questions.
1 reply 0 retweets 4 likes -
Yup, if we were convinced all aspects of it were right we’d be all SHIP IT. A prototype is a good first step though. :)
2 replies 0 retweets 3 likes -
Replying to @stubbornella @flackrw and
I joke, of course, there are a lot steps between prototype and actually shipping a thing :)
1 reply 0 retweets 2 likes
And the higher-level the API, the more the steps!
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.