If you're building animated dialogs/menus, you should be building them with this and transition-behavior: allow-discreet, workarounds/hacks should only be used where absolutely necessary as they will rapidly become deadweight.
Accept where we are today, but build with the near future in mind.
I came across this article today and it’s the best explanation of each frontend framework and their differences that I have yet read. But it made me wonder: is there a good, current book that explains the fundamentals and core concepts of JS, frameworks and the web platform? E.g. how the DOM works, how React deals with DOM, how non-React frameworks do DOM now, etc? Book/article recommendations appreciated! https://joshcollinsworth.com/blog/antiquated-react#webplatform#webdev
SvelteKit “Form actions” is the single most underrated feature. I use it to power 95% of the mutation happens to my projects, I no longer needs that much JSON API endpoints. It's dead simple as it leverages the native web form to send data, you can easily extend it using use:enhance or your own customized handler to provide a better UX.
TIL about the input[type=search]incremental#HTML attribute 1
Seems smart to have native debouncing built into the #WebPlatform, but as quickly as I've learned about it, I discovered Safari removed it in version 17.2 2 🤔
Anyone know why? The release notes just say it was "non-standard", but it was in every browser except Firefox 3 🤷♂️
The first acroynm-based tech stack I've been excited about since back before JAMstack became more focused on the J and A than the M – the AHA stack: https://ahastack.dev/
The specific frameworks/libraries are just implementation details, but their set of principles really resonates!
🎉 WebKit is moving it's position on the Navigation API to "support" 1 🎉
Hopefully it'll get implemented soon! 🤞 (it's been GA in Chrome since May 2022)
If you're not already aware of it's benefits: it gives us a far better progressive-enhancement than intercepting click/submit events, where we lose the native browser loading-feedback and have to manually adjust history with the History API.
The #StateOfHTML survey is a great way to discover #WebPlatform APIs you may not know exist or may not realise are now supported – you can even have a reading list emailed to you at the end 🙌🏻
I’ve been building for the web for 20 years, stick to the Web Platform where possible, and I only scored 82%! There’s always something new and exciting to learn in our industry.
The Web Applications Working Group has published Web Share API as a W3C Recommendation. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example,...
Yesterday I was invited to a Twitter Space Google I/O as GDE webplatform and discussed, among other things, new features coming to the web (https://twitter.com/i/spaces/1yNGaNOrVXnJj).
I'm genuinely happy to see we go towards more user-centric and inclusive, accessible experiences with a lot of new CSS features and APIs.
We need to embrace that flexible nature of the web.
I also would love it, if more designers could start getting interested into all those new features and in how to use them for a greater experience. You don't need to learn to code. But, understanding what a browser can do will for sure help build better, more user-centric experiences in the next couple of years.
So, yeah, I'm super happy to see where the web platform is going those days.
WEB SHARE API IS A W3C RECOMMENDATION (www.w3.org)
The Web Applications Working Group has published Web Share API as a W3C Recommendation. This specification defines an API for sharing text, links and other content to an arbitrary destination of the user’s choice. The available share targets are not specified here; they are provided by the user agent. They could, for example,...