-
-
Notifications
You must be signed in to change notification settings - Fork 465
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
Setting leading
of NavigationAppBar permanently sets the Leading icon of NavigationPane when it's displayMode is top🐛
#284
Labels
bug
Something isn't working
Comments
Do these comments answer your question? Or perhaps I have misunderstood. |
I'm having this issue too. Minimal code to reproduce below. See the blue import 'package:fluent_ui/fluent_ui.dart';
void main() {
runApp(const MyApp());
}
class MyApp extends StatelessWidget {
const MyApp({Key? key}) : super(key: key);
// This widget is the root of your application.
@override
Widget build(BuildContext context) {
return FluentApp(
title: 'Flutter Demo',
home: NavigationView(
appBar: const NavigationAppBar(
leading: CircleAvatar(),
title: Text('Flutter Demo'),
),
pane: NavigationPane(
displayMode: PaneDisplayMode.top,
items: [
PaneItem(
icon: const Icon(FluentIcons.add),
),
],
),
),
);
}
} |
Okay, understood. This is effectively a bug. |
Can i work on this BTW. I am new to contributing. |
This was referenced Apr 12, 2022
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When you set a leading icon using leading property of NavigationAppBar, it permanently sets the Leading icon of NavigationPane when it's displayMode is top. And I do not find any property or methods which can be used to override that icon.
To Reproduce
Code to Reproduce
Expected behavior
If this is bug, it must be resolved. If this is a hidden feature, there must be another property of NavigationPane to override the leading Widget.
Screenshots
P.S. I this is a bug, I would be grateful in helping contributing to it.
The text was updated successfully, but these errors were encountered: