Make sure we touch README.mozilla so that we can track what version we're on.
I don't really want to wait for our patches to get uplifted, but lets see how the timing goes. If we do have local patches, I'd like the landing of this to be in a three part patch set - the first one to undo our changes and get angle back to what it was in 2214; the second to just update to 2403; the third one to add our changes on top.
We should also investigate the flags ANGLE has and see if we're doing the right thing.
Stuff in WebGLShaderValidator.cpp, ChooseValidatorCompileOptions function.
(In reply to Milan Sreckovic [:milan] from comment #2) > We should also investigate the flags ANGLE has and see if we're doing the > right thing. I did do this in the past (maybe when I did the WebGLShaderValidator code), and cross-compared what we do with WRT Chromium.
There is a performance impact observed after this update, marked down as https://bugzilla.mozilla.org/show_bug.cgi?id=1210683.
Marking affected for 43.
(In reply to Liz Henry (:lizzard) (needinfo? me) from comment #10) > Marking affected for 43. That doesn't make sense to me. This didn't land until 44.
I'll find you on irc, there was a reference to this from another bug.
I misunderstood, thanks for the explanation Jeff!