Twitter | Search | |
Jake Archibald
Googler. I want the web to do what native does best, and fast. No thoughts go unpublished. 'IMO' implicit.
55,926
Tweets
1,729
Following
57,749
Followers
Tweets
Jake Archibald Sep 21
We changed the defaults here to remove this common gotcha
Reply Retweet Like
Jake Archibald Sep 20
He's long dead so he probably won't.
Reply Retweet Like
Jake Archibald Sep 20
You literally just talked about the benefits of the block button. No need to melt because someone used it.
Reply Retweet Like
Jake Archibald Sep 20
Replying to @tomwang1013 @aerotwist
As HTML is loaded, it's streamed to the parser and DOM is created. The browser may render with some portion of the HTML loaded. Eg, load with a throttled connection. You'll see content way before the page has fully loaded.
Reply Retweet Like
Jake Archibald Sep 20
Replying to @seangates
Am I holding it wrong?
Reply Retweet Like
Jake Archibald Sep 20
Replying to @mountain_ghosts
All Killa No Filla - funny deep dives into the lives of serial killers. Skeptics with a K - science & skepticism stuff. These are my faves.
Reply Retweet Like
Jake Archibald Sep 20
Replying to @seangates
404 🤨
Reply Retweet Like
Jake Archibald Sep 20
Replying to @tomwang1013 @aerotwist
No. Defer happens at domready, but half-loaded pages can render
Reply Retweet Like
Jake Archibald Sep 20
Hanging out at GDD China, watching and talk about building PWAs.
Reply Retweet Like
Jake Archibald Sep 20
Probably because they hid EVIL BACKWARDS DRUGS MESSAGES in their songs. I love this radio clip of Chris Morris winding up a true believer of this stuff
Reply Retweet Like
Jake Archibald Sep 20
Replying to @tomwang1013 @aerotwist
Async JS will run once it's loaded. This may be before or after first render.
Reply Retweet Like
Jake Archibald Sep 20
Replying to @ReasonableCoder
Puppeteer is a good bet as you can control network settings.
Reply Retweet Like
Jake Archibald Sep 19
Replying to @LeoWWong
All browsers have service worker now. If you override fetch you can do whatever you want with the response: const realFetch = fetch; window.fetch = async function(request, opts) { const response = await realFetch(request, opts); return response; };
Reply Retweet Like
Jake Archibald Sep 19
Replying to @LeoWWong
You could overwrite window.fetch. But if you really want to intercept requests then service worker is the answer.
Reply Retweet Like
Jake Archibald Sep 19
Replying to @LeoWWong
I don't think you can intercept all page requests with XHR. Eg, can you intercept an <img src="…"> request?
Reply Retweet Like
Jake Archibald retweeted
rahulrc Sep 13
If there's one thing we can all agree on, it's cake! Thanks for the birthday present 🎂😀
Reply Retweet Like
Jake Archibald Sep 18
Replying to @tomwang1013
Yep. As per the diagram, it just opens the door. It won't skip anything along the way.
Reply Retweet Like
Jake Archibald Sep 18
Replying to @devninjapirate
I've opened . Can you list the other issues there?
Reply Retweet Like
Jake Archibald Sep 18
Replying to @tomwang1013
In terms of the diagram I used, the door to the render steps opens on vsync.
Reply Retweet Like
Jake Archibald Sep 18
Replying to @tomwang1013
I cover vsync in the event loop talk. Vsync dictates when the compositor and event loop perform their render steps. But if either of those threads are busy, they'll be delayed.
Reply Retweet Like