<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - LibreOffice 7.2 introduced addition popup for read only file that shouldn't be showing" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143971#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - LibreOffice 7.2 introduced addition popup for read only file that shouldn't be showing" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143971">bug 143971</a> from <a class="email" href="mailto:mikekaganski@hotmail.com" title="Mike Kaganski <mikekaganski@hotmail.com>"> Mike Kaganski</a> <pre>(In reply to Mikeyy - L10n HR from <a href="show_bug.cgi?id=143971#c7">comment #7</a>) IMO moving this to an infobar is unrelated to the problem here (I don't have any personal preference on dialog-vs-infobar approach myself FWIW). There should be *no* potentially confusing, unneeded information for user whenever the program *is able* to figure that the information is unneeded/wrong, even if that means that we need a more complex code. In case when application can detect that the file will never get "unblocked", like when we are opening a file from a known-temporary location, the suggestion to notify when available should *not* appear. Anything else is just trying to make application's fault less intrusive.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>