Thomas Steiner (@tomayac)

Now at

The below is an off-site archive of all tweets posted by @tomayac ever

July 25th, 2020

I’ve also just PR’ed the new browser-nativefs 💾 version into @excalidraw (see, so all dare-devils 🤘💀 using Excalidraw on Chrome Canary can continue to profit from the Native File System API.

via Twitter Web App

🗣 Heads up: Chrome 86 will introduce BREAKING changes to the Native File System API: #NativeFS.

🛀 Users of the browser-nativefs 💾 library can relax: I’ve taken care of it for you in v0.10.0: Just

via Twitter Web App

@MightyBoosh_ @ChromiumDev FWIW, we offer a library, browser-nativefs, that maybe makes your life easier today already:

via Twitter Web App

@MightyBoosh_ @ChromiumDev Not currently. The feature request is tracked in, though.

via Twitter Web App

@jaffathecake Coincidentally suggested it to @dluzar just the other day…

via Echofon

@addyosmani @sulco @Ev1l_Ash In a way `<frameset>` was SPA before SPA.

via Echofon

addyosmani Native <iframe> lazy-loading is coming to the web! <iframe loading=lazy> defers loading offscreen iframes until a user scrolls near them.

Now in the HTML standard & supported in Chrome.

via Twitter Web App (retweeted on 11:43 AM, Jul 25th, 2020 via Echofon)

@scottjehl @rob_dodson @briankardell @justinfagnani On the other hand `part` not allowing for descendant selectors encourages not nesting one’s element too deeply. If DOM depth becomes a problem, maybe there’s potential for splitting up the element ev

via Echofon

In case you ever wondered why the response of a `fetch()` call is a stream:

via Twitter for iPhone

@rmondello Congratulations on the work anniversary! 🎂

via Echofon in reply to rmondello

@MikeEsto 💏 Nice article. By the way, we have landed native Screen Wake Lock support in NoSleep.js, so users of this library will automatically use the API if their browser supports it.

via Echofon in reply to MikeEsto