BackdropFilter not working as expected #3273
-
DescriptionI'm trying to achieve the following css rule: In this demo it works just fine: But for some reason in my project it only shows this: Even though i do see it in the generated index.css like this: Any idea what can cause this? It's driving me nuts.. thanks. Link to Reproductionhttps://play.panda-css.com/Kxqd_8YZKN Steps to reproduce
JS FrameworkReact / Next.js Panda CSS Version0.53.7 BrowserLatest Chrome for both tests Operating System
Additional InformationNo response |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 2 replies
-
|
That's weird. Sounds things that come to mind:
Definitely a strange error. |
Beta Was this translation helpful? Give feedback.
-
|
Has the actual issue been identified? Next 16 is probably going to be released this week and turbopack is going to be the default for dev and prod builds. |
Beta Was this translation helpful? Give feedback.
-
|
This is still an issue in nextjs version 16.1.6 w/ bun. |
Beta Was this translation helpful? Give feedback.
-
|
parcel-bundler/lightningcss#695 (comment) this comment brought me on the right track! LightningCSS seems to be removing the unprefixed backdrop-filter if the order is wrong. in my case there was no order to fix. so I edited their answer to readd the backdrop-filter! plugins: [
{
// Based on https://github.com/parcel-bundler/lightningcss/issues/695#issuecomment-3780316192
name: 'Fix backdrop-filter for LightningCSS',
hooks: {
'cssgen:done': ({ artifact, content }) => {
if (artifact !== 'styles.css') return
// LightningCSS removes the unprefixed `backdrop-filter`, leaving only
// `-webkit-backdrop-filter`. This adds it back after the prefixed version.
return content.replace(
/(-webkit-backdrop-filter:\s*)([^;]+;)(?!\s*backdrop-filter:)/g,
'$1$2\n backdrop-filter: $2'
)
},
},
},
], |
Beta Was this translation helpful? Give feedback.


I think the solution is by downgrading your nextjs version to 15.0.4 @sjaakbanaan and it will work again if you want to keep using
--turbopack. If you are okay with not using the--turbopackfeatures, you can disabled it just like what @segunadebayo suggest, I've tried both solution and it works.