You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default file-type-filter in the file-picker that is opened with "Send image", does only show a single file-type (jpg) by default.
There is currently no option for showing all (compatible) image-file-types at the same time.
Steps to Reproduce
Open a chat.
Use "Send Image" to choose an image-file.
Notice that the file-type-filter is set to "jpg" by default.
Open a folder with an image in PNG- or WebP-format, and notice that it is not visible by default.
Expected Behavior
There should be an option for the file-type-filter to show all (compatible) image-file-types, and it should be the default-setting.
App Version
1.25.0 - Flatpak
Additional Platform Information
Debian GNU/Linux Testing (Trixie)
Additional Context
I sometimes try to send an image in WebP-format with "Send Image", and then wonder why i cannot find it, until i notice that i have to switch the file-type-filter. Because that is more complicated, i almost always use "Send file" instead.
The text was updated successfully, but these errors were encountered:
Bug Description
The default file-type-filter in the file-picker that is opened with "Send image", does only show a single file-type (jpg) by default.
There is currently no option for showing all (compatible) image-file-types at the same time.
Steps to Reproduce
Expected Behavior
There should be an option for the file-type-filter to show all (compatible) image-file-types, and it should be the default-setting.
App Version
1.25.0 - Flatpak
Additional Platform Information
Debian GNU/Linux Testing (Trixie)
Additional Context
I sometimes try to send an image in WebP-format with "Send Image", and then wonder why i cannot find it, until i notice that i have to switch the file-type-filter. Because that is more complicated, i almost always use "Send file" instead.
The text was updated successfully, but these errors were encountered: