Skip to content

[Impeller] IconButton.outlined border appears visually broken / clipped on certain devices #182708

Closed

Description

@Hladenkyi

Steps to reproduce

Run the following minimal reproduction sample (standard Flutter IconButton gallery example)

Expected results

All IconButton variants render with a clean, fully closed circular border as per Material 3 specification.

Actual results

The circular border of IconButton.outlined appears visually broken — the outline is incomplete or clipped, making the button look malformed. This issue is only reproducible with Impeller enabled (default renderer on Android). Running with --no-enable-impeller resolves the issue completely, which suggests this is an Impeller rendering bug.

Code sample

Code sample
import 'package:flutter/material.dart';

/// Flutter code sample for [IconButton].

void main() {
  runApp(const IconButtonApp());
}

class IconButtonApp extends StatelessWidget {
  const IconButtonApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(colorSchemeSeed: const Color(0xff6750a4)),
      title: 'Icon Button Types',
      home: const Scaffold(body: ButtonTypesExample()),
    );
  }
}

class ButtonTypesExample extends StatelessWidget {
  const ButtonTypesExample({super.key});

  @override
  Widget build(BuildContext context) {
    return const Padding(
      padding: EdgeInsets.all(4.0),
      child: Row(
        children: <Widget>[
          Spacer(),
          ButtonTypesGroup(enabled: true),
          ButtonTypesGroup(enabled: false),
          Spacer(),
        ],
      ),
    );
  }
}

class ButtonTypesGroup extends StatelessWidget {
  const ButtonTypesGroup({super.key, required this.enabled});

  final bool enabled;

  @override
  Widget build(BuildContext context) {
    final VoidCallback? onPressed = enabled ? () {} : null;

    return Padding(
      padding: const EdgeInsets.all(4.0),
      child: Column(
        mainAxisAlignment: MainAxisAlignment.center,
        spacing: 10,
        children: <Widget>[
          IconButton(
            icon: const Icon(Icons.filter_drama),
            onPressed: onPressed,
          ),

          // Filled icon button
          IconButton.filled(
            onPressed: onPressed,
            icon: const Icon(Icons.filter_drama),
          ),

          // Filled tonal icon button
          IconButton.filledTonal(
            onPressed: onPressed,
            icon: const Icon(Icons.filter_drama),
          ),

          // Outlined text button
          OutlinedButton(
            onPressed: onPressed,
            child: const Icon(Icons.filter_drama),
          ),

          // Outlined icon button
          IconButton.outlined(
            onPressed: onPressed,
            icon: const Icon(Icons.filter_drama),
          ),
        ],
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration Image

Logs

Logs
[Paste your logs here]

Flutter Doctor output

Doctor output
[✓] Flutter (Channel stable, 3.41.2, on Ubuntu 24.10 6.11.0-29-generic, locale uk_UA.UTF-8) [57ms]
    • Flutter version 3.41.2 on channel stable at 
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 90673a4eef (3 дні тому), 2026-02-18 13:54:59 -0800
    • Engine revision 6c0baaebf7
    • Dart version 3.11.0
    • DevTools version 2.54.1
    • Feature flags: enable-web, enable-linux-desktop, enable-macos-desktop, enable-windows-desktop, enable-android, enable-ios, cli-animations, enable-native-assets, omit-legacy-version-file, enable-lldb-debugging,
      enable-uiscene-migration

Activity

  1. changed the title [-]IconButton.outlined border appears visually broken / clipped on certain devices[/-] [+][Impeller] IconButton.outlined border appears visually broken / clipped on certain devices[/+] on Feb 21, 2026
  2. added
    in triagePresently being triaged by the triage team
    has reproducible stepsThe issue has been confirmed reproducible and is ready to work on
    e: impellerImpeller rendering backend issues and features requests
    on Feb 23, 2026
  3. mbcorona commented on Feb 23, 2026

    @mbcorona
    Member

    Hi @Hladenkyi, thanks for reporting and the code sample.

    I was able to reproduce this locally. The circular border of IconButton.outlined is malformed when running with the default Impeller renderer, but renders perfectly clean when passing the --no-enable-impeller flag.

    Labeling team-engine for investigation.

  4. removed
    in triagePresently being triaged by the triage team
    on Feb 23, 2026
  5. gaaclarke commented on Mar 2, 2026

    @gaaclarke
    Member

    @walley892 can you check if these circles are going through the SDF renderer please?

    In general these seem like they may just be artifacts from MSAA, maybe?

  6. gaaclarke commented on Mar 2, 2026

    @gaaclarke
    Member

    @mbcorona what device were you using when you took the screenshots?

  7. added
    P2Important issues not at the top of the work list
    on Mar 2, 2026
  8. mbcorona commented on Mar 2, 2026

    @mbcorona
    Member

    @gaaclarke Pixel 8 Simulator and physical Samsung Galaxy S10 Android 15, #183002 reported happening on Android 16

  9. gaaclarke commented on Mar 2, 2026

    @gaaclarke
    Member

    @mbcorona thanks. So, these sort of artifacts are expected for the Android emulator, because the Android emulator does not have support for MSAA (the antialiasing technique we use on device).

    As part of our work to support Impeller better on desktop we will be implementing some techniques to smooth out these drawings. I'd like to take advantage of those techniques on the Android Simulator too. Those issues are tracked mostly in the #183031 issue.

  10. jason-simmons commented on Mar 2, 2026

    @jason-simmons
    Contributor

    Reproduced this on a Pixel 6a.

    Confirmed that it started with the circle SDF change (a41146c)

    #183083 has another example that shows a similar issue after the SDF commit.

  11. gaaclarke commented on Mar 3, 2026

    @gaaclarke
    Member

    The triager has nice pictures of this problem at #183083 (comment)

  12. 13 remaining items

  13. mimoguz commented on Mar 11, 2026

    @mimoguz

    @gaaclarke

    Comparison

    Better, less jagged. Still, there’s almost no antialiasing going on I think?

    Doctor summary (to see all details, run flutter doctor -v):
    [✓] Flutter (Channel main, 3.42.0-1.0.pre-488, on Fedora Linux 43 (Workstation Edition) 6.18.16-200.fc43.x86_64, locale en_GB.UTF-8)
    [✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0)
    [✓] Chrome - develop for the web
    [✓] Linux toolchain - develop for Linux desktop
    [✓] Connected device (2 available)
    [✓] Network resources
    
  14. gaaclarke commented on Mar 11, 2026

    @gaaclarke
    Member

    Better, less jagged. Still, there’s almost no antialiasing going on I think?

    Technically there is anti-aliasing via MSAA (except in cases like the android emulator). #183418 will add more with sdfs.

  15. walley892 commented on Mar 12, 2026

    @walley892
    Contributor

    Heyo!

    If you're running on an android emulator - there may be no MSAA going on.

    I've cooked up #183536 and included screenshots of your initial demo app running with the change - hopefully it looks okay!

  16. github-actions commented on Mar 26, 2026

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  17. locked as resolved and limited conversation to collaborators on Mar 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

P2Important issues not at the top of the work listcp: stablecherry pick this pull request to stable release candidate branche: impellerImpeller rendering backend issues and features requestshas reproducible stepsThe issue has been confirmed reproducible and is ready to work onteam-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