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 gfx/wr #3866

Merged
merged 2 commits into from Feb 19, 2020
Merged

Commits on Feb 19, 2020

  1. Bug 1612620 - Fixing dashed/dotted border issue Android devices with …

    …Adreno. r=jnicol
    
    On GLES, the default shader behaviour is to use highp(32bit) integers
    in the vertex shader and mediump(16bit) integers in the fragment shader. This
    causes issues in the border shader due to bitshifting with 16 bits. The
    fix here is to only shift by 8 bits as the data can be represented in a
    16bit integer and forcing mediump in the vertex shader as well.
    
    Differential Revision: https://phabricator.services.mozilla.com/D62784
    
    [ghsync] From https://hg.mozilla.org/mozilla-central/rev/a2caf09a5e7cadd78e5a12c4d715d3f0c996e48c
    Kris Taeleman authored and moz-gfx committed Feb 19, 2020
  2. Bug 1615694. Declare our render targets up front to ANGLE. r=kvark

    This should remove the allocation and copy in
    TextureD3D::ensureRenderTarget() in some situations.
    
    Differential Revision: https://phabricator.services.mozilla.com/D62952
    
    [ghsync] From https://hg.mozilla.org/mozilla-central/rev/e49c57e82a1923cde9170a74bff2d136c58759d2
    jrmuizel authored and moz-gfx committed Feb 19, 2020
You can’t perform that action at this time.