Skip to content

fix: android share screen #2437

Open
Gibbz wants to merge 1 commit intokrille-chan:mainfrom
Gibbz:fix/android-share-screen
Open

fix: android share screen #2437
Gibbz wants to merge 1 commit intokrille-chan:mainfrom
Gibbz:fix/android-share-screen

Conversation

@Gibbz
Copy link
Copy Markdown

@Gibbz Gibbz commented Dec 18, 2025

share screen previously was overlaping the navigation and notification bars

Thank you so much for your contribution to FluffyChat ❤️❤️❤️

Pull Request has been tested on:

  • Android
  • iOS
  • Browser (Chromium based)
  • Browser (Firefox based)
  • Browser (WebKit based)
  • Desktop Linux
  • Desktop Windows
  • Desktop macOS

@Gibbz Gibbz requested a review from krille-chan as a code owner December 18, 2025 08:46
@Gibbz
Copy link
Copy Markdown
Author

Gibbz commented Dec 18, 2025

Fix for this issue
#2221

required Widget Function(BuildContext context) builder,
}) => showDialog<T>(
context: context,
useSafeArea: false,
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does change it for all showScaffoldDialog uses. Have you checked all of them? Maybe better make this configurable, keep the default to false and only for the share screen make it true?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah! I'll have a dig and see what other dialogs are using it then test them.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have checked the uses of this dialog. they are all working fine. There are several forwarding and sharing screens using it.
(image_viewer.dart, chat_list.dart, and chat.dart)

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ops not sure if i should use resolved or not

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants