Flags in language drop-down not displayed in web deployment

[ampapplarsen]

Expected behavior (required)

When a language selection dropdown is presented, a flag should be displayed for each language option item.

Current behavior (required)

Instead of a flag, a burger menu like icon (three black horizontal bars) is shown instead.

To Reproduce (required)

1. Enable more than one language option
2. Add the language selection widget
3. Publish to web
4. Observe the above widget

Context (required)

I want to display language selection dropdowns beautifully as I have a lot of language translations.

Screenshots / recordings

Screenshot
Web deployment with the bug live. Please go to the Settings page

[Pepino-GR]

Hi ampapplarsen,

I can reproduce this issue, when I open your Webpage with the Safari Webbrowser. If I open it in Google Chrom, it works as expected.

[Pepino-GR]

[ampapplarsen]

Hi ampapplarsen,

I can reproduce this issue, when I open your Webpage with the Safari Webbrowser. If I open it in Google Chrom, it works as expected.

Still a bug, though? Safari has a substantial share of the browser market.

[bulgariamitko]

Yes but this is not FF issue it should be Flutter issue. I will make this as not a bug for now and let's FF team decide.

[ampapplarsen]

That's interesting. To the no-coder it's hard to discern where FF stops and F begins.

FF has two F's so it's twice as good.

[Pepino-GR]

For me it is not mainly a Flutter or FlutterFlow issue. There are two ways to fix the issue. The problem occurred because Safari handles the code different than Chrome. So one way to fix it is on Safari by Apple. The other way to fix it is on the Flutter or FlutterFlow site.

FlutterFlow use a Flutter Package to shows the flags. And it seems, that this does not work the same way on Chrome and Safari.

[Pepino-GR]

With the new Safari Version 16.1 (18614.2.9.1.12), the behavior changed.

[ampapplarsen]

No, this is my custom code. I just went ahead and built my own instead. I don't think these small issues will get fixed fast, so might as well steam ahead.

I'm sorry for the confusion.

Issue persists though and I am just trying to help iron out these things for those that follow.