#csswg
At the CSSWG, folks in the WebKit team have been making incredible progress prototyping freeform/diffusion gradients. We're trying to replicate what Affinity and Adobe Illustrator do.

Does anyone know how I can contact the devs of Affinity? We're trying to understand what 'spread' does.
November 17, 2026 at 12:11 AM
La reciente decisión de CSS Working Group (CSSWG) aborda un debate técnico crucial: la relación entre los botones y los espacios vacíos en el diseño web. Esto no solo afecta la estética, sino también la funcionalidad y la accesibilidad.

https://norvik.tech/news/analisis-cursors-csswg
November 17, 2026 at 1:05 AM
Looks like I am not the first to think of/ask for this: github.com/w3c/csswg-dr…

Get you 👍s and use cases on ofer at the issue!!

#css #csswg
[css-env] border radius · Issue #6259 · w3c/csswg-drafts
In some operating systems (such as macOS), the browser has a rounded corner of the border. When the page content sets the border, need to adapt this rounded corner Proposal Add safe-border-top-left...
github.com
November 16, 2026 at 10:17 PM
버튼에 cursor: pointer 적용하기

CSSWG 가 appearance: base-… 를 사용하는 버튼과 여러 폼 요소에 cursor: pointer 를 적용하는 커서 규칙을 채택하기로 합의함 이번 결정은 브라우저의 기존 기본 스타일을 바꾸는 것이 아님 . 새 규칙은 기본 외형을 지정하는 appearance: base-… 요소에 적용됨 해당 사용자 에이...
버튼에 cursor: pointer 적용하기
CSSWG 가 appearance: base-… 를 사용하는 버튼과 여러 폼 요소에 cursor: pointer 를 적용하는 커서 규칙을 채택하기로 합의함 이번 결정은 브라우저의 기존 기본 스타일을 바꾸는 것이 아님 . 새 규칙은 기본 외형을 지정하는 appearance: base-… 요소에 적용됨 해당 사용자 에이...
news.hada.io
November 16, 2026 at 5:00 AM
New blog post: “Contents Pseudo-Element”.

blog.kizu.dev/contents-pse…

I want a `::contents` #css pseudo-element. I know I am not alone — and if you want it too, I invite you to upvote the corresponding CSSWG issue and provide your use cases there.
ContentsContentsContentsContents Pseudo-ElementPseudo-ElementPseudo-ElementPseudo-Element
# ContentsContentsContentsContents Pseudo-ElementPseudo-ElementPseudo-ElementPseudo-Element Published on: November 18, 2026 Categories: Wishlist 4, CSS 98 Current music: THE MOLICE — _HOLE!!_ <a href="https://molice.bandcamp.com/track/hole">THE MOLICE<span class="nowrap"> —</span> HOLE!!</a> Current drink: Peppermint Tea This is more of an express last-minute post: I want a `::contents` pseudo-element. I am not alone! In 2018 Oriol Brufau opened a “Add a ::contents pseudo-element” CSS Working Group issue, and it has plenty of upvotes, being in the top 50 of open CSSWG issues (we have many of them). The idea is pretty simple: an ability, for any element, to create an inner wrapper just through CSS. This is something I always wanted — there is a myriad of use cases. I don’t have time to make them into proper examples, but if you’ve been writing CSS for a long time, you’ve likely stumbled upon use cases for this. Here is a short list of things that come to my mind right away: * Flex and Grid create anonymous boxes — if you want to do something with them, you can’t, and you start adding extra divs. * Elements with `overflow: auto` often behave not very well when you want to make them flex or grids too. Or — often you want all the content of such a scroller to be wrapped into one big element. * Often, you want to style your `::before` and `::after` differently from your content, and for some things in CSS you can’t achieve it without wild hacks right now, like when you want to override `text-decoration`. * Container size or style queries — you can’t use them for the element itself, so often you have to add extra wrappers. And just think about all the cases where you added an extra nested div or span just for styling. Having such wrapper being available only through CSS could simplify so many things! We even already got `: details-content`, which is very similar. Anyway! This CSSWG issue was open for a very long time. And while there were no progess, just recently, Florian Rivoal added it to the CSSWG’s Future Agenda. So, eventually, we will discuss it in our meetings. I hope this will come sooner rather than later — and if you want this pseudo-element to appear in CSS too — upvote this issue, and add your own use cases there.
blog.kizu.dev
November 18, 2026 at 11:46 PM
New blog post: “Cursors”.

https://blog.kizu.dev/cursors/

In which I take a cursory glance at a victory that CSSWG did hand out to us in this pointless debate about if buttons have more in common with blank space compared to links.
CursorsCursorsCursorsCursors
# CursorsCursorsCursorsCursors Published on: November 13, 2026 Categories: CSSWG 8, CSS 96, Opinion Current music: Envy — _Connected Voice_ <a href="https://envy.bandcamp.com/track/conneted-voice">Envy<span class="nowrap"> —</span> Connected Voice</a> Current drink: Peppermint Tea Three weeks ago, at a CSS Working Grouping meeting, we discussed an issue “Cursors for base appearance”, and resolved on the following: > The CSS Working Group just discussed [css-forms-1] Cursors for base appearance, and agreed to the following: > > * RESOLVED: Adopt cursor rules in the last comment. > * SUMMARY: Pointer = “click this thing”, text cursor says “prepare to enter text”, grabbing hand says “drag this”. > One of the rules from the “last comment” mentioned there is select, option, input[type=checkbox], input[type=radio], button, input[type=button], input[type=submit], input[type=reset], input[type=color], input[type=image], ::file-selector-button { cursor: pointer; } Or, if we were to remove all non-button selectors, button { cursor: pointer; } That is, of course, not a change to the default styles in the browser — this is a rule for elements that will have an `appearance: base-…`. Also note that, this user agent style will be very much overrideable — no `!important`. Anyone who does not like `cursor: pointer` on buttons and other similar elements, are free to override it to `default` (or anything else) in their stylesheets. The rest of us can, I guess, celebrate? I was always on the side of this decision. I published my “Correct Cursor on Active Elements” article in 2013. In 2017, I opened my first CSSWG issue — “Change the pointer cursor to indicate any interactive element”, which led to a change in a non-normative part of the spec. Since then, I did not see any new arguments in this debate. I will not repeat everything that I argued about, but one of the most common counter-arguments that I read today is “OS does not do it”. Did you see that “OS”? When was the last time your OS innovated anything in the UI? Did it become easier to use over years? Many of people with this argument ask, thinking that this will be a good question, something like “What next — change the cursor in the OS?!”. I mean… Yes? I would be happy with that. When I look at like half of the (non-native) apps in my desktop OS, they have `cursor: pointer` on interactive elements. Cinny, Discord, Signal, Slack, Steam, VS Code — some of the apps that I have before me. When I use apps that _do not_ change the cursor to anything other than `default`, I cringe. Default cursor does not communicate anything. It does one job well — point at a specific pixel. It could do more. In the issue, many people came with dislikes and their arguments against `cursor: pointer`. I want to aknowledge one argument that I fully agree with — it would be great if buttons and links would have different cursors. And also, regular links should have cursors different from the links that are opened in new tabs. We need more cursors. But if we were to look at those three things: * Blank space on the page. * Buttons. * Links. And then had only two cursors to assign to all of them, I know which ones I will assign to which. And I will never understand anyone thinking that buttons have more in common with blank space than with links.
blog.kizu.dev
November 13, 2026 at 8:41 PM
this is going to be amazing. I have been frustrated by the lack of this ability for years so very glad to see its going thru
Yesterday, the CSSWG accepted my proposal for mesh gradients and diffusion curve gradients! Want to make gradients like this natively in CSS? Well, we've started the work on it. It's coming! Here's the Explainer: https://github.com/w3c/csswg-drafts/blob/main/css-images-5/explainers/2d-gradients.md
mastodon.social
November 14, 2026 at 8:38 PM
Le masonry en CSS natif, c'est le serpent de mer du front. Le ticket date de 2017. Masonry.js, c’est bientôt fini !

Saleh Mubashar explique chez Piccalilli pourquoi ça a pris autant de temps : Grid étendu, Flexbox ou display à part, le CSSWG a tourné en rond avant de choisir `display […]
Original post on mastodon.social
mastodon.social
November 13, 2026 at 11:11 PM
The CSSWG resolved on naming the values last week: github.com/w3c/csswg-dr...
November 8, 2026 at 3:46 AM
Finally put up the CSSWG proposal for this. github.com/w3c/csswg-dr...

Let’s see where it goes!
November 6, 2026 at 11:26 PM
New blog post: “Four Resolutions From TPAC 2026 CSSWG Meetings”.

https://blog.kizu.dev/four-tpac2026-csswg-resolutions/

Last week TPAC 2026 happened. I attended it remotely, and participated in a bunch of #css Working Group meetings.

There were many discussions and resolutions, but I want to […]
Original post on front-end.social
front-end.social
November 6, 2026 at 10:52 PM
We're still waiting for standards positions from Mozilla github.com/mozilla/stan... and WebKit github.com/WebKit/stand...

There has been progress on the issue for grid lanes, as of the CSSWG at TPAC which I mentioned in rachelandrew.co.uk/archives/202...
CSS reading-flow · Issue #1056 · mozilla/standards-positions
Request for Mozilla Position on an Emerging Web Specification Specification title: CSS reading-flow Specification or proposal URL (if available): https://drafts.csswg.org/css-display-4/#reading-flo...
github.com
November 8, 2026 at 6:22 AM
All I know is that there’s been a lot of discussion for a long time about the grid lane behavior :)

github.com/w3c/csswg-dr...
[css-grid] Masonry layout in CSS Grid 3 has potential to cause accessibility problems with reading order. · Issue #5675 · w3c/csswg-drafts
Assuming all authors code their masonry grid in a valid reading order, screen reader user who are non-visual will have no problem with it. But once we introduce visual screen reader users, low visi...
github.com
November 7, 2026 at 8:38 PM
I would love to see someone from the CSSWG team do a 2026 Web technologies review and share what's to come from their perspective. I would really love to read that.
November 5, 2026 at 4:10 PM
Cursors for base appearance. CSSWG settled the long-standing debate: form controls with appearance: base get cursor: pointer when clickable, grab on range sliders, and not-allowed when disabled. #css #html

github.com/w3c/csswg...
November 2, 2026 at 11:00 AM
Thanks for the article. I appreciate that you represented what I said fairly and didn't twist my words.

To expand on my idea of distinct cursors for links, check out my comment on the original W3C issue: github.com/w3c/csswg-dr...
[css-forms-1] Cursors for base appearance · Issue #14251 · w3c/csswg-drafts
Disabled controls should indicate that they are unusable. Proposed to add: :is(input, textarea, select, button):disabled { cursor: not-allowed; } Also <select> and <button> should indicate they are...
github.com
November 3, 2026 at 11:53 PM
The CSS Working Group resolved to use `cursor: pointer` for buttons and other clickable form controls in the new user-agent styles for `appearance: base`
November 2, 2026 at 1:12 PM
github.com/orgs/w3c/pro... is the project you're looking for.
CSSWG agenda TPAC 2026 • w3c
CSSWG agenda TPAC 2026
github.com
November 1, 2026 at 6:58 PM