When you open a save as dialog by default the name of the file is highlighted (which is good as it's assumed that if you're saving as you want to change the name) but the algorithm that detects the file name is wrong as it looks for the first period in the file vs. the last. Steps: Open writer Save as "this vs. that" without the quotes Save as again Observed: "This vs." is highlighted Expected "This vs. That" is highlighted (up to the . of .odt) Marking as: Minor -- doesn't prevent high quality work but can slow down workflow a bit Low -- easy work around, default of low seems accurate Probably an easy hack so marking as such
I do not reproduce it under Win7 64bit with 4.1.4.2 and 4.2.1.0.0+ Build ID: 88cd9632e081f5839cf9fddf60cbff0c099e2968 TinderBox: Win-x86@42, Branch:libreoffice-4-2, Time: 2014-01-09_22:46:56
Interesting - so for you it highlights the whole name all the way up until the .odt? If this is Linux only that would be really surprising but I suppose you never know
Created attachment 92801 [details] save dialog Win7 @Joel this is what I see anymetime I resave. the whole filename and extension as well are highlighted. post yours to show me the difference.
and for me - under Ubuntu - there is never anything selected with "File save as"
Wow looks like linux only
Created attachment 92821 [details] FileNameInUbuntu
@Cor - I don't use LibreOffice dialogs. When I turn those on nothing is selected (another bug report I suppose, or at least an enhancement request)
I can confirm this behaviour under Linux (Ubuntu) with system dialogs.
Indeed Linux only. Can't reproduce using Mac OSX. Full filename is selected
I wish to work on this bug, can someone provide with a little bit of help? :) Regards, Rachit Gupta
@Rachit - fantastic. I just want to confirm you've already built LibreOffice ? I will try to find someone to give some code pointers but if you haven't already built we'll need you to start there :) Let me know if you need assistance
Hmm =) so this could be at the intersection of what the gtk+ file selector does magically for you, and what we do. AFAIK we don't put the extension into the file-picker there but append it ourselves; of course if the user adds one that is fine; lets hope '. that' is not a filter name ;-) if you want to save as: foo.doc.doc you will not be able to enter 'foo.doc' - you have to enter it in full; Anyhow - Rachit - you'd want to git grep for the gtk file selector API: git grep -3 gtk_file_chooser will show you where that is =)
@Joel, yes i have built LO, I have already solved an EasyHack task ;) @Joel and @Michael, I think the problem is only in the systems with GTK as their Desktop Environment. My friend uses Kubuntu, and there is no highlight on the file name (as also mentioned in Comment#4).
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Rachit Gupta committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=55eb86699d7d4b2151530e9a0b3ca2e99033595b fdo#74064 The filename gets properly highlighted in the Save As dialog. The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
@Rachit - thanks! Going to test it out as soon as I can get this build done
Verified :)
Thanks Joel :)
This change causes regression I just noticed. Filed Bug 76466.
Judging by the situation, perhaps this bug should have been fixed on the GTK3 side?
Kohei Yoshida committed a patch related to this issue. It has been pushed to "master": http://cgit.freedesktop.org/libreoffice/core/commit/?id=9dc4377c91b00585519abfd4fc1528393fe84e4a Revert "fdo#74064 The filename gets properly highlighted in the Save As dialog." The patch should be included in the daily builds available at http://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: http://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Sorry. I have to conclude that this is not a right fix. Simply ignoring our auto extension flag for the GTK dialog has other consequences. I would still explore the avenue that perhaps this is a bug in the GTK file picker itself, not ours.
(In reply to comment #22) > Sorry. I have to conclude that this is not a right fix. Simply ignoring > our auto extension flag for the GTK dialog has other consequences. > > I would still explore the avenue that perhaps this is a bug in the GTK file > picker itself, not ours. Either that, or perhaps look into whether or not we can control selection of file name in the GTK file chooser dialog, and try to fix this there if that's the case.
No problems. If this was not the right fix, it's good that it is reverted. I'll try to work on the right fix :)
please give an update of the current bug status with latest LibO 4.4.5.2 release. if issue persists set status to NEW, if it's gone to RESOLVED WORKSFORME @Rachid Gupta if the bug is still present and you are not working anymore on this issue, please remove yourself from the "Assigned to" field
Hi @tommy27 I am really sorry for no updates on this issue. It completely slipped from my mind. I have unassigned myself from this issue. Someone else can take this up and solve it. Changing the status of the bug to "NEW" Regards Rachit Gupta
(In reply to Rachit Gupta from comment #26) > ... > > Changing the status of the bug to "NEW" > just to be sure, does this mean you retested with latest LibO release and confirm the bug is still present?
(In reply to tommy27 from comment #27) > (In reply to Rachit Gupta from comment #26) > > ... > > > > Changing the status of the bug to "NEW" > > > > just to be sure, does this mean you retested with latest LibO release and > confirm the bug is still present? My apologies but I am not currently actively involved with LibreOffice development. I don't have the current builds either.
Lack of highlight still occurs in Lo 5.0.3.2 linux-mint 17.3 Cinammon.Build ID: 1:5.0.3~rc2-0ubuntu1~trusty2
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Still reproducible with Version: 6.3.0.4 Build ID: 057fc023c990d676a43019934386b85b21a9ee99 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-AT (de_AT.UTF-8); UI-Language: en-US
Dear Joel Madero, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 146416 has been marked as a duplicate of this bug. ***
Dear Joel Madero, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug