| GitHub | https://github.com/break-stuff/ |
| https://twitter.com/stuffbreaker | |
| Bluesky | https://bsky.app/profile/stuffbreaker.bsky.social |
| https://www.linkedin.com/in/burton-smith-48132a34/ |
| GitHub | https://github.com/break-stuff/ |
| https://twitter.com/stuffbreaker | |
| Bluesky | https://bsky.app/profile/stuffbreaker.bsky.social |
| https://www.linkedin.com/in/burton-smith-48132a34/ |
A conversation with a coworker re-triggered an intrusive thought that I find myself returning to regularly while working in a firm in the grips of AI influences:
Teams and engineering processes are like fish in tanks. There's a careful balance of the nitrogen cycle that keeps delicate organics alive; above a certain pH, it's just not plausible to believe things will keep working. But to understand effects, we have to take into account causes and add the effect of time.
* CSS Zoom inheritance fixes
* Custom Element Registry
* Auxiliary mouse button values in MouseEvent.button
* lighter operator in SVGFECompositeElement
* WebAuthn CTAP PIN/UV Auth Protocol 2
* Multiple microphone capture on macOS
* WebRTC network slicing on iOS
* MediaDeviceInfo in secure contexts only
They are all new in Safari 26.4 beta!
https://developer.apple.com/documentation/safari-release-notes/safari-26_4-release-notes
Are teams using #TypeScript declaration maps to provide a better go-to-definition experience for developers?
I've used source maps, but I don't think I've provided declaration maps.
When you are in an #html file, and you want to go-to-definition for a custom element, what do you think the behavior should be? Should it go to:
- type definition
- JS file where the class is defined
- CEM entry
- something else
🚀 Big news: We’re now sponsored by the Google Chrome team through the Chrome Performance Fund!
Together, we’re advancing web performance and modern tooling—integrating Baseline + Web Features into our next module-replacements release to deliver smarter, environment-aware suggestions. Huge thanks for the support 🙏
read more here:
https://e18e.dev/blog/the-year-ahead-2026.html#sponsored-by-google-chrome
I updated my article on reducing #WebComponent FOUC to include details on how to choose an appropriate timeout.
#html #css #javascript
https://dev.to/stuffbreaker/reducing-fouc-with-web-components-1jnh