Popover API Sliding Nav
Here’s a nifty demo of popover
but it’s not for what we’d traditionally consider a modal dialog.
It’s very exciting to see the support for popovers—I’ve got a use-case I’m looking forward to playing around with.
Although there’s currently a bug in Safari on iOS (which means there’s a bug in every browser on iOS because …well, you know).
Here’s a nifty demo of popover
but it’s not for what we’d traditionally consider a modal dialog.
In an earlier era, startups could build on the web and, if one browser didn’t provide the features they needed, they could just recommend that their users try a better one. But that’s not possible on iOS.
I’m extremly concerned about the newest bug in iOS 18:
Whaa? That’s just shockingly dreadful!
One dev team made the shift from React’s “overwhelming VDOM” to modern DOM APIs. They immediately saw speed and interaction improvements.
Yay! But:
…finding developers who know vanilla JavaScript and not just the frameworks was an “unexpected difficulty.”
Boo!
Also, if you have a similar story to tell about going cold turkey on React, you should share it with Richard:
If you or your company has also transitioned away from React and into a more web-native, HTML-first approach, please tag me on Mastodon or Threads. We’d love to share further case studies of these modern, dare I say post-React, approaches.
The thinking behind the minimal JavaScript framework, Strawberry:
Even without specialized syntax, you can do a lot of what the usual frontend framework does—with similar conciseness—just by using
Proxy
andWebComponents
.
I made an offhand remark at the Clearleft Christmas party and Trys ran with it…
Also, tipblogging.
The sound of worlds colliding.
Caches are for copies.
Progressive, not regressive, enhancement.
Technically, websites can do just about anything that native apps can do. And yet the actual experience of using the web on mobile is worse than ever.