Download it now!
Bug 42573 - Filter Selection Dialog Should Be in Two Columns (Name | Extension) & Have Some Non Random Ordering
Summary: Filter Selection Dialog Should Be in Two Columns (Name | Extension) & Have So...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
Hardware: All All
: low trivial
Assignee: Joel Madero
: 51029 (view as bug list)
Depends on:
Reported: 2011-11-03 16:01 UTC by eschamp
Modified: 2013-07-08 21:20 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:

Screenshot (86.23 KB, image/png)
2012-01-04 13:54 UTC, tester8

Note You need to log in before you can comment on or make changes to this bug.
Description eschamp 2011-11-03 16:01:01 UTC
The menu of filters that pops when LO doesn't recognize the doc you want it to open appears to be in random order. I'm requesting that it be changed to a listing of filer names arranged alphabetically.

Comment 1 Cor Nouws 2011-11-04 01:13:59 UTC
Looking at it now, I have two remarks:
- when typing a character (e.g. m) the list selects the next item starting with that character;
- isn't it logic that on top we have ODF, and then the next most used?
Comment 2 eschamp 2011-11-04 08:54:26 UTC
I don't know if we're looking at the same thing. When I'm presented with a menu, I usually click on one of the choices; i.e., I do not type anything, so I don't understand your comment.
Comment 3 tester8 2012-01-04 13:54:09 UTC
Created attachment 55136 [details]

Did you mean that dialog? You can navigate on it by typing first letter. But IMHO this dialog is still too complex. May be good idea is to divide it on two columns: name of format and tipycal extension.
Comment 4 Joel Madero 2012-06-26 15:48:59 UTC
@tester8 I think your solution seems feasible, going to change the title to better reflect the situation. Also going to mark as NEW and prioritize as TRIVIAL -> Low
Comment 5 Joel Madero 2012-07-10 21:08:57 UTC
Can you post a file that you have that actually triggers the dialog? I have tried everything I can think of to trigger it and I never see it. I'm marking as NEEDINFO until the file is posted. Thanks!
Comment 6 Andras Timar 2012-07-16 09:55:43 UTC
*** Bug 50801 has been marked as a duplicate of this bug. ***
Comment 7 Andras Timar 2012-07-16 10:39:17 UTC
*** Bug 51029 has been marked as a duplicate of this bug. ***
Comment 8 Andras Timar 2012-07-16 10:40:16 UTC
(In reply to comment #6)
> *** Bug 50801 has been marked as a duplicate of this bug. ***

Sorry, I clicked on the wrong browser tab.
Comment 9 QA Administrators 2013-05-27 16:54:28 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here:

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team
Comment 10 QA Administrators 2013-07-08 21:20:39 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO