-
-
Replying to @mathias
@mathias@slightlylate@zachleat@bram_stein in couple of words, what is bad?1 reply 0 retweets 0 likes -
Replying to @nekrtemplar
@nekrtemplar: craaaazy polling overhead. On slow devices it swamps other things threads could be doing. /cc@mathias@zachleat@bram_stein3 replies 0 retweets 1 like -
Replying to @slightlylate
@slightlylate@nekrtemplar@mathias@zachleat We’re going to use scroll events (no more polling) soon, which should help on older browsers.2 replies 0 retweets 1 like -
Replying to @bram_stein
@bram_stein: The issue isn't older browsers so much as slower devices. Your polling is _out of control_ /cc@nekrtemplar@mathias@zachleat2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate just to be clear: scroll events are an alternative to polling for font loading polyfills.@bram_stein@nekrtemplar@mathias1 reply 0 retweets 0 likes -
Replying to @zachleat
@zachleat: oh, yeah, I know, and it's a good thing..but scroll events have other issues. /cc@bram_stein@nekrtemplar@mathias1 reply 0 retweets 0 likes -
Replying to @slightlylate
@zachleat: particularly they don't do the Event Listener Options thing to make sure they're passive. /cc@bram_stein@nekrtemplar@mathias4 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate would be great to do some tests against TypeKit/polling problems@zachleat@bram_stein@mathias3 replies 0 retweets 0 likes -
Replying to @nekrtemplar
@nekrtemplar: but this pwns typekit site: isSmallScreen: function() { return window.innerWidth <= 767 },@zachleat@bram_stein@mathias3 replies 0 retweets 0 likes
@nekrtemplar: I see http://typekit.com go unresponsive for 7+ seconds thanks to that script.
/cc @zachleat @bram_stein @mathias
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.