<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: a quick way to pick a ODF version on save" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134976#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: a quick way to pick a ODF version on save" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134976">bug 134976</a> from <a class="email" href="mailto:heiko.tietze@documentfoundation.org" title="Heiko Tietze <heiko.tietze@documentfoundation.org>"> Heiko Tietze</a> <pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=134976#c6">comment #6</a>) > ... we have the "Edit filter settings" checkbox in the Save As dialog. Bad solution IMHO. It interrupts the common and simple workflow of saving a file and presents the user a sequence of dialogs she has to go though with no clear feedback what happens. For example, does clicking Save in the file picker dialog mean the file is saved even when the follow-up settings dialog is cancelled? If we place legacy formats more prominently I suggest not one odf entry in the filter list but also "ODF v1.2 Text Document (.odt)". However, support for the QA team might be of interest for the development but is not user-centered design.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>