@angustweets @brianleroux @joemccann not really "necessary". You could maintain second api with an internal promise.
-
-
Replying to @polotek
@polotek@angustweets@joemccann ya, idk. I think adding these to the DOM is going to cause much woe in the coming years1 reply 0 retweets 0 likes -
Replying to @brianleroux
@brianleroux@polotek@angustweets@joemccann : look, it needs to be .ready().then(). The sooner we get over it the better1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@brianleroux what's the reason it needs to be? Isn't this api vs implementation?2 replies 0 retweets 0 likes -
Replying to @polotek
@polotek@brianleroux : you want a global promise object? Or an getter that always returns different things? Didn't think so.2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate@polotek I don't understand why those are the only options. I trust your opinion obv.1 reply 0 retweets 0 likes -
Replying to @brianleroux
@brianleroux@polotek : ready() could take callbacks if it also returns a new promise each time and hooks em up.1 reply 0 retweets 1 like -
Replying to @slightlylate
@slightlylate@brianleroux yeah absolutely. It returns the same promise. If you passed a callback it just called then(cb) internally first.1 reply 0 retweets 1 like -
-
@brianleroux @polotek : most dom apis return void so can be retrofitted.
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.