Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix backdrop-filter blur (add prefixes) #4182

Closed
wants to merge 5 commits into from

Conversation

100100101
Copy link
Contributor

Backdrop-filter didn't work in Chrome modile (ios) or Safari mobile (ios).
Now works in Chrome modile (ios) in Safari mobile (ios).

I also tested on Android Chrome, but the effect does not work there.

I'll take a closer look a little later.

I also propose to make auxiliary classes for forced affixing of backdrop-filter
Something like

.translucent-type-1 {
	-webkit-backdrop-filter: saturate(180%) blur(var(--f7-bars-translucent-blur));
  	-moz-backdrop-filter: saturate(180%) blur(var(--f7-bars-translucent-blur));
  	backdrop-filter: saturate(180%) blur(var(--f7-bars-translucent-blur));
}
.translucent-type-2 {
    -webkit-backdrop-filter: blur(15px);
    -moz-backdrop-filter: blur(15px);
    backdrop-filter: blur(15px);
}
...

@nolimits4web
Copy link
Member

Hi,

Thanks, but it doesn't require these prefixes. Plus prefixes are controlled by autoprefixer, and webkit prefix is already there as you can see in Kitchen Sink:

screenshot

@100100101
Copy link
Contributor Author

I used tree shaking less files, like this:
Снимок экрана 2023-06-01 в 11 56 44
And not using postcss autoprefixer, and have this:
_ 2023-06-01 _ 11 52 02
Now i add autoprefixer to my vite configuration:
Снимок экрана 2023-06-01 в 12 13 52
And now all working good, like full bundle (but with tree shaking ability) like this:
_ 2023-06-01 _ 11 51 27
Perhaps you should mention this point in the documentation
Thank you)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants