Simon Pieters

Simon Pieters

@zcorpan.bsky.social

Web standards engineer at Mozilla

274 followers149 following106 posts

Simon Pieters reposted

I had no idea that the subject of the RICG’s canonical responsive images examples endured in the specification to this very day:

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.

engineering.squarespace.comSquarespace & Web Standards: How We Helped Bring HTML Video & Audio Lazy Loading to Today’s Browsers — Squarespace Engineering BlogAt Squarespace, many of our core products are built on web standards, and our engineers are constantly pushing the boundaries of the web’s capabilities. Occasionally, those boundaries reveal a limitat...

Simon Pieters reposted

Is anybody still using xml/HTML polyglots for anything moder (Syntax that is valid in both html and xml) Wondering whether those are something that needs to be considered for future HTML enhancement or a thing of the past...

Simon Pieters reposted

We mentioned on Winging It that we might show some of our favorite browser tips. Here's one of many that I find delightful. If you are working with shape-outside, then Firefox has a great path editor. I made a quick video to show how it works.

Simon Pieters reposted

Want to build faster websites? Here's how: - Learn how browsers parse, layout & paint - Treat JS as a tool, not the foundation(!) - Favor static HTML or server side rendering at all times - Use Core Web Vitals alongside other metrics to learn shortfalls, improve and iterate Then keep doing that.

Simon Pieters reposted

Okay gang, those who sling HTML, CSS, JS, which _Firefox_ bugs are blocking you? Which features do you think need improving? What new features would you like to see? What work would you prioritise? Big or small, bonus points for linking to a bug (even more for filing bugs then linking them)!

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.

developer.mozilla.orgHTMLDialogElement: closedBy property - Web APIs | MDNThe closedBy property of the HTMLDialogElement interface indicates the types of user actions that can be used to close the associated <dialog> element. It sets or returns the dialog's closedby attribu...

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…

github.comMSEdgeExplainers/EventPhases/explainer.md at main · MicrosoftEdge/MSEdgeExplainersHome for explainer documents originated by the Microsoft Edge team - MicrosoftEdge/MSEdgeExplainers

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

thenewstack.ioInterop Unites Browser Makers To Smooth Web InconsistenciesFor the past four years, major browser vendors have collaborated to improve web interoperability by coordinating enhancements to inconsistent browser implementations.

Simon Pieters reposted

Browsers used to have a feature where you could add new context menu items. Is this worth reviving? Yes or No? Would you use it as a developer? What use cases do you have? Would you want this as a user?

Simon Pieters reposted

Lots of sites have this "hovercard" style pattern on links which shows you a cut-down preview of the page behind the link - often times with additional interactions. I wonder if anyone has any more examples? Especially sites which do this (display a rich tooltip) on non-links.

Simon Pieters reposted

Friday marked my last day at GitHub. I spent almost 8 years building one of my most favourite websites. It was truly a pleasure working on it, but I could feel my interest waning, not least due to React & the push for AI. Today I start at my new job... with totally renewed excitement!

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...

developer.mozilla.org<h1>–<h6>: The HTML Section Heading elements - HTML: HyperText Markup Language | MDNThe <h1> to <h6> HTML elements represent six levels of section headings. <h1> is the highest section level and <h6> is the lowest. By default, all heading elements create a block-level box in the layo...
Simon Pieters@zcorpan.bsky.social

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

As it's Friday (here at least) can all you webdevs do me a favour and make this simple code change: 1. Search for `aria-labeledby` in your codebases. 2. Change it to `aria-labelledby` (note the double L) 3. Submit a PR. 4. Congratulate yourself for your Friday contribution.

Simon Pieters reposted

And yet another polyfill appears to have poisoned the standards well. This time for scoped custom element registries. People never learn. 🫠

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.

buff.lyNavigating the Web Platform CheatsheetAs a web developer, navigating the web platform isn't always easy. Here are ways to keep track of what you can use, of what's new in web browsers, and ways you can influence the development of the…

Simon Pieters reposted

8 1/2 years ago Chrome started explicitly warning that scripts shouldn't use document.write And yet today, the biggest generator of these warnings seems to be Google's AdTech stack

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...

View full thread

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...

View full thread

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...

- The default rendering was implemented in browsers, but not the heading level in the accessibility tree. - Websites started to use sectioning elements, but didn't expect automatic heading levels. It was not possible for browsers to change that without breaking user expectations.

Simon Pieters reposted

Looking at the Interop Project scores since 2021 — look at how much higher the overall “interop” score (the black line) is for 2024 over the previous years! Wow. Great job everyone who was involved in 2024, from those who helped plan to those who fixed browser bugs or implemented new features.

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

htmlforpeople.comHTML for PeopleHTML isn't only for people working in the tech field. It's for everyone. Learn how to make a website from scratch in this beginner friendly web book.