- From: Damian via GitHub <noreply@w3.org>
- Date: Fri, 02 Jan 2026 11:34:12 +0000
- To: public-css-archive@w3.org
Thanks Sebastian — I think you’re right that the API should be future-proof and naturally accommodate the other logical blur variants from #11134. Given that, I’m going to revise the proposal toward a dedicated function `linear-blur()` with gradient-like stop list syntax, rather than overloading `blur()`. In the interest of momentum, I’d still propose tackling progressive (linear) blur first as the initial implementation focus (common 0 → N scrim case, default `to bottom`), but within a syntax that can later extend to additional stops/offsets and `radial-blur()` / `conic-blur()`, etc. If you see any pitfalls with `linear-blur()` as the long-term shape (parsing, perf/implementation constraints, interactions with `backdrop-filter`), I’d love to hear them. -- GitHub Notification of comment by damian-dp Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13285#issuecomment-3705141876 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 January 2026 11:34:13 UTC