You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use a background image in css or tw, for the navbar, the doc-theme's css --tw-backdrop-* modifiers prevent the image from appearing as anything but blurred.
I tried this in firefox and safari.
I tried setting my own settings to override, and they did somewhat, but seemed to get blocked at opacity. I'm able to disable them in developer tools to see the expected result and what is blocking it but not able to accomplish this with code:
Unfortunately that does not seem to solve this issue.
!backdrop-filter-none shows up and in FF the code for the backdrop filters show as struckthrough/disabled, but when I uncheck --tw-backdrop-opacity in both spots that is when my nav-bar image shows up.
I'm using the .nextra-nav-container selector.
I've also tried it with ! and specifying all of the backdrop filters with !important and still I need to uncheck the backdrop filters below even though they are struckthrough/disabled and then the image will show up not blurred/faded.
In other words even though things appear to be communicated correctly to the engine, it is not working. Some kind of bug? But is reproduced in Safari and Chrome.
When I use a background image in css or tw, for the navbar, the doc-theme's css --tw-backdrop-* modifiers prevent the image from appearing as anything but blurred.
I tried this in firefox and safari.
I tried setting my own settings to override, and they did somewhat, but seemed to get blocked at opacity. I'm able to disable them in developer tools to see the expected result and what is blocking it but not able to accomplish this with code:
I tried using @apply backdrop-filter-none to disable the backdrop filters but it doesn't seem to override those set by the theme.
Is there some other way I'm missing here? Thanks for your help.
The text was updated successfully, but these errors were encountered: