Skip to content

fix: Blur #132

Description

@nferhat

The current implementation of blur in the compositor right now is pretty bad. Notably:

  1. It relies on optimized blur (aka. X-Ray blur) by default, which is a sane default but many people want to have "true blur"

  2. True Blur (when enabled) destroys any damage tracking done by us. My initial implementation was extremely naive and I didn't
    bother to test it further, however this must change as more people are picking up the compositor and leaving such a lackluster
    implementation bothers me.

  3. The implementation breaks on scaled monitors.

  4. The implementation can potentially break on monitors that are not logically placed at (0, 0) (IE. the "origin" of the global space)

A new implementation would rely on #100, and new advancements, notably Smithay/smithay#1946 and Smithay/smithay#1910, to accurately track damage. Implementations are going to be heavily inspired from Niri's and cosmic-comp's, even though they are based on this one, they figured out a lot of the details I skipped.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or requestgood first issueGood for newcomershelp wantedExtra attention is needed

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions