Hello Everyone,

I hope you all had a wonderful week. Mine was also a good one. With this, let’s start with this week’s reading material…

📚 To Read

The Unlocked Possibilities of the :has() Selector

CSS :has() selector is starting to come out in stable browsers now. And with that, it becomes important to see how it can solve your CSS issues and simplify it. It’s already there in Stable Safari since Safari 15.4 and will be there in stable Chrome 105. Firefox’s support is not there yet, but with the way, it is moving it shouldn’t be far behind.

Masonry? In CSS?!

Masonry layouts have always been hard and impossible without using JavaScript, so I’m very excited for this. Currently, there is no browser support and Firefox allows this behind a flag which you can use to test it, but when it happens this will be very, very useful.

The energy to suggest change

This was an interesting opinion piece. Loved reading it.

Stop supporting Internet Explorer!

When I say ‘Stop supporting IE’ it means to me that I won’t go the extra mile to get unsupported features working in Internet Explorer, but still make sure Internet Explorer users get the basics, and can use the site.

How to be LGBTQIA+ inclusive 🏳️‍⚧️🏳️‍🌈

How to be more inclusive with your language and actions.

Body Margin 8px

No one needs this style, and yet, this is there by default in all the browsers. So, how did it become the default when literally no one needs/wants it.

Why the HTML Outlining Algorithm was removed from the spec – the truth will shock you!

Recently, the HTML spec changed to replace current outline algorithm with one based on heading levels. So the idea that you could use

for a generic heading across your documents, and the browser would “know” which level it actually should be by its nesting inside

and other related “sectioning elements”, is no more.

😃 Something that made me smile

https://twitter.com/standardpuppies/status/1545663851408273408?s=20&t=iWE1fqJp2A3uMMTJ3u50QA