Skip to content

CSS3 filter support [$300] #1428

Open
shaidshark/NativeScript
#1

Description

@Ivshti

It would be great if visual effects could be applied to elements/backgrounds/images, such as blur, grayscale, etc.

Perhaps CSS3 filter implementation or some other API?

For example:

Page#test {
  filter: blur(20);
  background-image: url("res://test");
}

Would blur the entire Page element.


There is a $300 open bounty on this issue. Add to the bounty at Bountysource.

Activity

  1. enchev commented on Jan 26, 2016

    @enchev
    Contributor

    Hey @Ivshti,

    Very good suggestion - added as backlog!

  2. changed the title [-]Image/background effects[/-] [+]CSS3 filter support[/+] on Jan 26, 2016
  3. 40x commented on Nov 8, 2016

    @40x

    @enchev any update on this yet?

  4. patrickpereira commented on Jan 28, 2017

    @patrickpereira

    +1

  5. viniciodeltoro commented on Feb 23, 2017

    @viniciodeltoro

    +1

  6. toddanglin commented on Mar 3, 2017

    @toddanglin

    This would be a very powerful "nice to have" capability! Would enable some cool new ways of styling {N} apps. Adding my +1.

    Notably, the only plugin available for image filters today is Android only. Adding this to CSS after 3.0 would help extend capabilities to iOS.
    https://github.com/bradmartin/nativescript-image-filters

  7. felixkrautschuk commented on May 12, 2017

    @felixkrautschuk
    Contributor

    Are there any updates, is this feature already planned for a future release?
    Would be definately a nice addition for the NativeScript framework.

  8. sserdyuk commented on May 25, 2017

    @sserdyuk

    @enchev Is there a way to vote for it other than leaving another comment? I'm definitely interested!

  9. Cayan commented on May 25, 2017

    @Cayan
    Contributor
  10. added and removed on Oct 15, 2018
  11. sanved77 commented on Jul 10, 2019

    @sanved77

    This would definitely be a very useful feature

  12. changed the title [-]CSS3 filter support[/-] [+]CSS3 filter support [$300][/+] on Jul 22, 2019
  13. vanderjuh commented on Aug 21, 2019

    @vanderjuh

    Is there any news about this topic? I really would like to have this possibility in my next projects. Thanks, guys :)

  14. cxrtisxl commented on Aug 30, 2019

    @cxrtisxl
  15. imnikkielyn commented on Sep 9, 2019

    @imnikkielyn

    Haha still not updated :(

  16. markus-gx commented on Sep 12, 2019

    @markus-gx

    Need this one too.. Any other alternative so far?

  17. BeBrito2004 commented on Jun 14, 2023

    @BeBrito2004

    Still nothing?

  18. vallemar commented on Jun 14, 2023

    @vallemar
    Contributor
  19. BeBrito2004 commented on Jun 16, 2023

    @BeBrito2004

    @vallemar thank you!

  20. added 2 commits that reference this issue on Apr 2, 2026
    22014f8
    e651fb9
  21. triniwiz commented on May 5, 2026

    @triniwiz
    Member

    Currently pending #11091

  22. Asobu01 commented on May 5, 2026

    @Asobu01

    I can take #1428.
    Start: reproducing the UI/layout issue and isolating the component/state that causes it.
    ETA: draft PR in ~8h.
    Deliverables: minimal UI fix aligned with current UX; quick before/after validation notes; PR with clear change summary. @Asobu01

  23. Asobu01 commented on May 5, 2026

    @Asobu01

    Quick follow-up on NativeScript/NativeScript#1428. I am still ready to start immediately and can post the first repro/checklist note before the draft PR if helpful. If you want me on this one, I can begin now. (@Asobu01)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions