filter()

Open Beginner friendly
#509 1 comment 41 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
68/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
css
Domain
frontend

Research direction

Start with the issue's browser-support table and the linked Can I Use, Web Features Explorer, and specification pages to understand the filter() feature. If you have relevant experience, use the provided comment template to describe a concrete use case and current workaround; done means adding focused feedback that follows the Code of Conduct.

Written by the indexing model from the issue text.

Description

CSS feature

This GitHub issue is for collecting web developer signals for filter().

The filter() CSS function applies one or more graphic effects to a CSS image, such as a background image. You can use functions, such as blur() and drop-shadow(), alone or combined to produce different effects. For instance, background: filter(url(image.png), blur(2px)).

Browser support

chromeunavailable edgeunavailable firefoxunavailable safariavailable
  • Chrome: not supported
  • Chrome Android: not supported
  • Edge: not supported
  • Firefox: not supported
  • Firefox for Android: not supported
  • Safari 9.1 (Mar 21, 2016)
  • Safari on iOS 9.3 (Mar 21, 2016)

Give us feedback

If you're pressed for time, but you want this feature to be available in all browsers, please give this issue a thumbs up 👍 reaction.

However, a much better guide for us is to know how you'd use this feature, and what you're having to do in the meantime. This helps us judge the priority versus other features.

Copy the template below in a comment, and add the details that matter to you.

## What I want to do with this feature

<!-- Add your specific use-cases, even if they seem obvious to you. -->

## What I'm having to do in the meantime

<!--
Are you having to use another feature instead, a polyfill, or is it blocking you completely?
Why are the alternatives worse than using this feature?
-->

All comments are expected to adhere to the Code of Conduct.

Learn more

You can learn more about this feature here:

Dominant language
TypeScript
Stars
111
Forks
13
Avg merge
1d 6h
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from web-platform-dx/developer-signals

All issues in web-platform-dx/developer-signals

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.