[material_ui] Port PR (#187247) from flutter/flutter to material_ui #11971
[material_ui] Port PR (#187247) from flutter/flutter to material_ui #11971elliette wants to merge 1 commit into
Conversation
…t shader now that it is no longer required by the Impeller GLES back end (#187247) flutter/flutter#186556 makes the behavior of the Y axis in the GLES back end consistent with other Impeller back ends. Shaders will render incorrectly if they continue to flip the Y axis based on "#ifdef IMPELLER_TARGET_OPENGLES".
|
@chunhtai What is the status of flutter/flutter#187807? Should this PR be ported to material_ui as is? Or does it need to use the |
|
Hi @jason-simmons after some investigation, the shader was sideloaded from flutter_tool with hardcoded file path, which mean it will use the flutter/flutter's shader file and ignore the version in material_ui. I think we won't need the migration for now. I am currently working on keeping the stretch shader to be permanently in flutter/flutter flutter/flutter#187960, I am still trying to figure out if there is something i missed before i can land the pr. If that PR lands, we don't need the |
|
Closing, this will be handled by flutter/flutter#188526 |
Most Material and Cupertino code was copied over from flutter/flutter in #11888, but a few PRs landed after that copy. This PR copies one of those PRs to this repo.
Ports over flutter/flutter#187247.
Work towards flutter/flutter#188441
Pre-Review Checklist
[shared_preferences]///).Test exemption: cherry-pick of PR from flutter/flutter
If you need help, consider asking for advice on the #hackers-new channel on Discord.
Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the
gemini-code-assistbot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.Footnotes
Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩2