Skip to content

Deprecate fragment shader setFloat #195357

New issue
New issue
Open
2 of 3 issues completed
Open
Deprecate fragment shader setFloat#195357
2 of 3 issues completed
Labels
P1High-priority issues at the top of the work listteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

Description

@gaaclarke
gaaclarke
opened on Oct 26, 2026

Now that we have the named API's we should just deprecate setFloat, there is no reason to need to use it anymore. And there are some outstanding usages where it can give surprising results ( see #194661 )

Activity

  1. gaaclarke
    added
    P1High-priority issues at the top of the work list
    team-engineOwned by Engine team
    on Oct 26, 2026
  2. github-project-automation
    added this to Flutter Engine Focuson Oct 26, 2026
  3. github-project-automation
    moved this to Todo in Flutter Engine Focuson Oct 26, 2026
  4. gaaclarke
    added sub-issues on Oct 26, 2026
  5. gaaclarke
    added
    triaged-engineTriaged by Engine team
    on Nov 2, 2026
  6. auto-submit
    added a commit that references this issue on Nov 2, 2026

    [material_ui] Use named uniforms instead of setFloat in InkSparkle (#…

    30d67e6
  7. Leapward-Koex
    added a commit that references this issue on Nov 3, 2026

    Use named uniforms instead of setFloat in StretchEffect (flutter#195372)

    852534a
  8. gmackall
    added a commit that references this issue on Nov 3, 2026

    Use named uniforms instead of setFloat in StretchEffect (flutter#195372)

    bbdbf0f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High-priority issues at the top of the work listteam-engineOwned by Engine teamtriaged-engineTriaged by Engine team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions