Simon Pieters
Simon Pieters
@zcorpan.bsky.social
Web standards engineer at Mozilla
274 followers149 following106 posts
Simon Pieters reposted
Simon Pieters reposted
New on the Squarespace Engineering Blog! Squarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy-Loading to Today’s Browsers. I'm real proud of the teamwork that went into this. Stay tuned for part 2 next week, which will cover dev best practices for using this new HTML standard.
Simon Pieters reposted
It's time for Interop 2026! This is a cross-browser effort where we agree on a set of focus areas to improve compatibility. Here's how things went in 2025, and what we're taking on for 2026: hacks.mozilla.org/2026/02/laun...
Simon Pieters reposted
Simon Pieters reposted
Simon Pieters reposted
Interop 2026 is now open for proposals! This is your chance to tell browser-makers which well-defined, well-tested features you wish had better support across browsers. ⬇️ Here's how ⬇️ github.com/web-platform...
Simon Pieters reposted
Gecko: Intent to Ship: CSS View Transitions L1
Simon Pieters reposted
Simon Pieters reposted
Simon Pieters reposted
Email addresses are very simple, and you will score highly in this quiz. e-mail.wtf
Simon Pieters reposted
Simon Pieters reposted
Simon Pieters reposted
“You might be familiar with SPAs, and MPAs, or actually RFWS ( Regular Fucking Web Sites)” — @cydstumpel.nl #CSSDay
Simon Pieters reposted
Hey friends, did you know you can make a modal <dialog> element dismissible by clicking outside (aka light dismiss) by adding `closedby=any` to it. That's it. That's all there is to it. <dialog closedby=any> developer.mozilla.org/en-US/docs/W... Chrome 134+, Firefox 140+, coming soon to Safari.
What is web compat? SmoothGate is a good case study and this article by @mths.be explains it well developer.chrome.com/blog/smooshg...
The src attribute on <img> is no longer required. github.com/whatwg/html/...
Simon Pieters reposted
Lots of folks fell for the "DOM is slow" marketing of certain frameworks, but DOM isn't slow. *Uncontrolled style read-back* is. But what if that wasn't a thing? Looking for feedback on a new proposal to control layout thrashing here: github.com/MicrosoftEdge/MS…
Simon Pieters reposted
If you ever wanted to use `sizes=auto` and were bummed out about Safari/Firefox support, Shopify now got a polyfill for ya! github.com/Shopify/auto...
Simon Pieters reposted
I take a deep dive into Interop 2025; why the project is there, how it picks what browser features to focus on each year, how well it's doing and what the big areas for this year are - a mix of cleaning up existing features and making sure new features arrive already interoperable
Simon Pieters reposted
Simon Pieters reposted
Simon Pieters reposted
I wrote an article that was #1 on the orange website for a bit earlier today news.ycombinator.com/item?id=4364...
Simon Pieters reposted
Blink: Intent to Deprecate and Remove: Deprecate special font size rules for H1 within some elements
Starting March 31, 50% of Firefox beta 138 users will have the change where <h1> always has the same UA style, even in article, aside, nav, section. Also, Lighthouse will fail a check if you have an <h1> without font-size specified. Advice for web developers: developer.mozilla.org/en-US/docs/W...
The backstory here is - h1 was specified to have automatic heading level based on the number of ancestor sections (or aside, article, nav). - The default rendering was specified to (roughly) match, such that <section><h1> would have the same font-size and margin as h2 - cont...
Simon Pieters reposted
Simon Pieters reposted
Simon Pieters reposted
Firefox stopped changing the font size of sectioned h1's and shows a warning if there are sectioned h1's without specified font-size and margin properties. Currently only in Nightly. codepen.io/matuzo/pen/P...
Simon Pieters reposted
I just made a thing: A collection of links for web developers to navigate the web platform more easily. 🟢 Places to follow progress and keep track. 🟣 Places to make your voice heard and influence the platform with your use cases.
Simon Pieters reposted
Simon Pieters reposted
Since apparently being a nice person is illegal in the US now, it’s time to pull out my most popular blog post ever. It’s called “survival tips for women in tech”, but I’m told it works for all genders and in countless industries. patricia.no/2018/09/06/s...
Simon Pieters reposted
If you want to get into web platform development and push features into browsers, I wrote a few words that I hope can be useful: blog.yoav.ws/posts/so_you...
Our team (DOM Core) has an open position: www.mozilla.org/en-US/career... Remote in any of Finland, Sweden, Denmark, Poland, Spain, Belgium, Netherlands, France, Germany, UK, Canada, or US.
The backstory here is - h1 was specified to have automatic heading level based on the number of ancestor sections (or aside, article, nav). - The default rendering was specified to (roughly) match, such that <section><h1> would have the same font-size and margin as h2 - cont...
Here's the new 2025 reset.css: h1 { margin-block: 0.67em; font-size: 2em; } Thank you for adopting this on all your sites! See github.com/whatwg/html/...
The backstory here is - h1 was specified to have automatic heading level based on the number of ancestor sections (or aside, article, nav). - The default rendering was specified to (roughly) match, such that <section><h1> would have the same font-size and margin as h2 - cont...
Here's the new 2025 reset.css: h1 { margin-block: 0.67em; font-size: 2em; } Thank you for adopting this on all your sites! See github.com/whatwg/html/...
Here's the new 2025 reset.css: h1 { margin-block: 0.67em; font-size: 2em; } Thank you for adopting this on all your sites! See github.com/whatwg/html/...
The backstory here is - h1 was specified to have automatic heading level based on the number of ancestor sections (or aside, article, nav). - The default rendering was specified to (roughly) match, such that <section><h1> would have the same font-size and margin as h2 - cont...
Here's the new 2025 reset.css: h1 { margin-block: 0.67em; font-size: 2em; } Thank you for adopting this on all your sites! See github.com/whatwg/html/...
Simon Pieters reposted
Simon Pieters reposted
Replying to @matuzo.at
@scottjehl.com have you ever seen @zcorpan.bsky.social's talk from HTML Day 2016: youtu.be/1fWvkIhvkjY?... He explains really nicely how the parser works for video sources as opposed to how it works with the picture element. 🤗
Simon Pieters reposted
🔥 Remember Internet Explorer’s Page Transitions? THEY’RE BACK BABY! 👾 Demo: ie-page-transitions.netlify.app ⌨ Repo: github.com/bramus/ie-pa... To configure these, use the meta tags from the olden days + load up the library. Works in IE 5.5–7.0, Chrome 126+, and Safari 18.2 (buggy).
Simon Pieters reposted
The State of JS 2024 survey results are now live! 2024.stateofjs.com/en-US A couple highlights 🧵
Simon Pieters reposted
I guess it is time to introduce Bluesky to my latest work, HTML for People. Anyone can make a website with HTML. No previous coding experience required. I cover everything you need to know to get started in an approachable and friendly way. And it’s free for all. 🚀 htmlforpeople.com