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

Sync changes from mozilla-central #3831

Merged
merged 3 commits into from Jan 14, 2020
Merged

Sync changes from mozilla-central #3831

merged 3 commits into from Jan 14, 2020

Commits on Jan 14, 2020

  1. Bug 1607746 - Part 1: Move opacity to its own shader in WebRender r=n…

    …ical
    
    Opacity is a common effect that is used and the opacit filter path is also used when a stacking
    context has an opacity of < 1. The brush_blend shader is slow since it has support for a large
    portion of CSS filters; however, opacity is used much more often than the rest of the filters.
    This patch adds a simple shader for opacity effects which bypasses the extra overhead in the
    brush_blend shader.
    
    Differential Revision: https://phabricator.services.mozilla.com/D59610
    
    [wrupdater] From https://hg.mozilla.org/mozilla-central/rev/b0226237c55e4a08f4deb622fc15fa1e85f39afc
    cbrewster authored and moz-gfx committed Jan 14, 2020
  2. Bug 1607746 - Part 2: Clean up passing filter mode to shader r=nical

    I removed the old opacity filter path in the brush_blend shader and cleaned up the filter mode
    constants in the shader so there are less magic numbers. This should help if/when we move more
    filters to their own shaders.
    
    Depends on D59610
    
    Differential Revision: https://phabricator.services.mozilla.com/D59611
    
    [wrupdater] From https://hg.mozilla.org/mozilla-central/rev/5cd63d35010f9bf9538a37fb330127d459b7ccc0
    cbrewster authored and moz-gfx committed Jan 14, 2020
You can’t perform that action at this time.