2019-07-31
787
#chrome#web design#what's new
Facundo Corradini
4338
Jul 31, 2019 â‹… 2 min read

New in Chrome 76: The frosted glass effect with backdrop-filter

Facundo Corradini Frontend developer, CSS specialist, best cebador de mates ever.

Recent posts:

Building A Serverless Postgres-Powered GraphQL API With Neon Db, Prisma Orm, And Apollo Server

Building a serverless GraphQL API with NeonDB and Prisma

Combine NeonDB, Prisma ORM, and Apollo Server within a serverless architecture to achieve a fully functional and scalable GraphQL API.

Nitish Sharma
Feb 8, 2024 â‹… 12 min read
Exploring Interaction To Next Paint, A New Core Web Vital

Exploring Interaction to Next Paint, a new Core Web Vital

Interaction to Next Paint was added to Google’s Core Web Vitals to provide a more comprehensive assessment of website interactivity.

Rahul Chhodde
Feb 7, 2024 â‹… 6 min read
Starlight Vs. Docusaurus For Building Documentation

Starlight vs. Docusaurus for building documentation

Explore Docusaurus and Starlight for building and customizing documentation websites, comparing their features such as sidebars, light/dark mode, and tabs.

Kapeel Kokane
Feb 6, 2024 â‹… 10 min read
Comparing Typescript State Management Solutions

Comparing TypeScript state management solutions

Dealing with state management in TypeScript provides benefits like type safety, code formatting, and error management.

Rashedul Alam
Feb 2, 2024 â‹… 17 min read
View all posts

2 Replies to "New in Chrome 76: The frosted glass effect with backdrop-filter"

  1. Instead of writing

    @supports (backdrop-filter: none) {

    backdrop-filter: blur(8px);

    }

    one should be writing

    @supports (backdrop-filter: blur(8px)) {

    backdrop-filter: blur(8px);

    }

    because you’re not in fact interested if the browser supports “backdrop-filter: none”, right?

    This is especially important once you realize that the same property (e.g. display) supports values with wide range of support by different UAs.

  2. Hi Mikko,

    The idea is to query the support of the property instead of the value. Querying for “backdrop-filter: none” will throw the same true / false result as querying for “backdrop-filter: 8px”, but allow us to change the value in a single place if for whatever reason we decide to do that in the future.

    It might not be such a dramatic impact in the small scale, but going with a query for property+value can lead to issues as the codebase grows and we start to have a lot of repetition and forgotten queries that doesn’t really make sense.

    Your point is certainly valid for properties such as display or position, but for most others, querying for property instead of property+value is a better approach in my opinion.

Leave a Reply