If you open the file open dialog, with the GTK3 VCL, and type something in the search bar - filtering the list - the file type box gets grayed out and you can no longer choose the file type / import filter.
Hello, the same behaviour is for example in Gedit, the dialog should be identical - system dialog. I don't think it's a bug.
(In reply to raal from comment #1) > Hello, the same behaviour is for example in Gedit, the dialog should be > identical - system dialog. I don't think it's a bug. Indeed. Idem in Geany. Closing as Not a Bug. Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #2) > Closing as Not a Bug. Don't you mean NOTOURBUG?
(In reply to Eyal Rozenberg from comment #3) > (In reply to Jean-Baptiste Faure from comment #2) > > Closing as Not a Bug. > > Don't you mean NOTOURBUG? No, I think it's not a bug it's a feature, because using the search field you can filter both the file name and the file type / extension. So the filtering list is not necessary when using the search field. For example, if you have several files in the folder with one named test1.odt and another named test1.pdf, you can find test1.pdf with the search criteria "test pdf". That said, you can report this issue against Gnome and see if a bug report is accepted. Best regards. JBF
(In reply to Jean-Baptiste Faure from comment #4) > No, I think it's not a bug it's a feature, because using the search field > you can filter both the file name and the file type / extension. Ah, so - you've misunderstood my bug report. The problem is not with filtering results. The problem is with the choice of input filter, i.e. the choice of how the document will be opened and with which module. The OS/DE typically assumes that opening a file is opening a file, and it's a single app which opens it, regardless of the controls used in the file open dialog box. We, however, give that list additional semantics. So it is _a_ bug that we cannot both use the file open dialog box' facilities for searching and filtering, and at the same time choose the appropriate input filter; and while this might have been resolved by more flexible OS/DE behavior, it is _our_ responsibility to allow the user to choose the import filter to be used. So it is not just _a_ bug, but _our_ bug.
I don't think there is anything we can do about it anyway when using the system gtk file picker, we don't have full control over that widget, so its all fairly moot IMO.
(In reply to Caolán McNamara from comment #6) > I don't think there is anything we can do about it anyway when using the > system gtk file picker, we don't have full control over that widget, so its > all fairly moot IMO. Well, actually, we could in theory only use the file picker's built-in file-type widget to make choices which don't affect the input filter, and use another widget, or more than one, for forcing the module to open and/or the input filter to use (with the default being automatic choice of everything of course). That may also partially address bug 151537. Still, that would be more of a mitigation than a solution. Another thing we could/should do is take this up with the GTK developers: https://gitlab.gnome.org/GNOME/gtk/
(In reply to Eyal Rozenberg from comment #7) > Another thing we could/should do is take this up with the GTK developers: > > https://gitlab.gnome.org/GNOME/gtk/ I've just filed: https://gitlab.gnome.org/GNOME/gtk/-/issues/5272 please consider going over there and supporting it on behalf of the project :-)