- writer document, start Navigator (docked) - Ctrl-N for new Writer Document > Focus is in Navigator should be in document. Try the same with Styles & FOrmatting window, then the focus is properly in the document
This behaviour doesn't occur when running Writer from the Launcher. It occurs with: -- File / New / Text document -- Running Writer from it's own icon Checked with various OSes: Xubuntu (10.04), Mageia 2, Windows 7.
Persisting with Ubuntu 14.10 LO Version: 4.3.3.2 Build ID: 430m0(Build:2)
In 4.4, component shortcuts in menu also cause this. That is a major regress.
*** Bug 86496 has been marked as a duplicate of this bug. ***
(In reply to Urmas from comment #3) > In 4.4, component shortcuts in menu also cause this. That is a major regress. Hi Urmas, Can you pls explain what you mean with this? thanks, Cor
** 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.0.5 or 5.1.0) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
This ugly bug still exists :\
** 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.2.5 or 5.3.0 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-20170306
Working with daily Linux dbgutil bibisect repository version 2017-03-21 running on debian-stretch, I see slightly different behavior: (*) In new document opened via <Ctrl>+N, the focus is in the navigator or document area, as it was in the previous window. (*) Upon redisplay of another Writer window, either by closing another LibreOffice window or by <Alt>+<Tab> from another LibreOffice window, focus goes to the navigator. Cor, I shall leave it to you to check my work and to change the bug summary here or to file a new report for the changed behavior.
Hi Terrence, (In reply to Terrence Enger from comment #9) > Working with daily Linux dbgutil bibisect repository version 2017-03-21 > running on debian-stretch, I see slightly different behavior: > (*) In new document opened via <Ctrl>+N, the focus is in the navigator or > document area, as it was in the previous window. For me that is not the case. Still as originally reported. (But it may be OS/config dependent, for sure)
** 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 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 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: 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
@Cor, Hi, From the comment made here [1], about not causing the same effect as in Writer, I found that the Navigator content grabbing focus is causing the Navigator to get focus when starting a new document while the Navigator is open. So can we just make the Writer Navigator behavior like the Calc Navigator and not have focus set to the tree list box when it is shown? [1] https://bugs.documentfoundation.org/show_bug.cgi?id=113250#c13
(In reply to Jim Raykowski from comment #12) > So can we just make the Writer Navigator behavior like the Calc Navigator > and not have focus set to the tree list box when it is shown? Not sure if that will help to prevent that the focus is *somewhere* but not in the document? If I read it, it may still be that the focus is on the Navigator's frame :D ?
This is the commit that added grab focus to tree in Writer Navigator commit fee0ef3ca44b92a6f2cd877bd2e02b87254ea3ab Author: Oliver Bolte <obo@openoffice.org>, Tue Nov 16 14:03:41 2004 +0000 (14 years ago) Committer: Oliver Bolte <obo@openoffice.org>, Tue Nov 16 14:03:41 2004 +0000 (14 years ago)
Here is a patch to test that doesn't focus on Navigator or Sidebar on show: https://gerrit.libreoffice.org/#/c/62337/
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/88cbc3ea2db8358bbedff01361f95f972f2b0231%5E%21 tdf#49684 Don't focus on Navigator or Sidebar on show It will be available in 6.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
It seems this still isn't resolved for gtk3? I used bibisect to find the commit which changed focus behavior for docking windows between gtk2 and gtk3. It is an awesome tool for debugging. Kudos to all who have contributed to it! On confirmation I will provide more details and a possible solution.
Hi Jim, Thanks for your efforts here! (In reply to Jim Raykowski from comment #17) > It seems this still isn't resolved for gtk3? In Version: 6.3.0.0.alpha0+ Build ID: 3bf82348bc73797fec61997dc4268a322299b3ff CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-01-06_08:29:45 Locale: nl-NL (nl_NL.UTF-8); UI-Language: en-US Calc: threaded I see two things: 1) - Have one document open with Navigator (F5), close the document. - Open the (or another document) > focus in document. Which is what this bug is about. So fixed, IMO. With gtk3. However.. 2) - Have document without Navigator open - hit F5 to open Navigator > focus still in document and not in Navigator, as was before (not sure if that started with your patch exactly) The use case for this is: - F5 (Navigator has focus) - use keyboard to go to a section (in Navigator) - enter to go to that place in the document File another bug for this?
(In reply to Cor Nouws from comment #18) Hi Cor, Here are the results I get with current master 6.3.0.0.alpha0+ > 1) > - Have one document open with Navigator (F5), close the document. > - Open the (or another document) > > focus in document. > Which is what this bug is about. So fixed, IMO. With gtk3. gtk3: for undocked Navigator focus is in Navigator for docked Navigator focus is in document gtk2: for undocked or docked Navigator focus is in document > However.. > 2) > - Have document without Navigator open > - hit F5 to open Navigator > > focus still in document and not in Navigator, as was before gtk3: for undocked Navigator focus changes to Navigator for docked Navigator focus remains in document gtk2: for undocked or docked Navigator focus remains in document
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/5a557821c647c1a499270a8a1188e23fc015f782%5E%21 Revert "tdf#49684 Don't focus on Navigator or Sidebar on show" It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jim Raykowski committed a patch related to this issue. It has been pushed to "libreoffice-6-2": https://git.libreoffice.org/core/+/35074dc5518e59284663ce85496b3cda406a25eb%5E%21 Revert "tdf#49684 Don't focus on Navigator or Sidebar on show" It will be available in 6.2.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Jim Raykowski committed a patch related to this issue. It has been pushed to "libreoffice-6-2-2": https://git.libreoffice.org/core/+/c58bc517af4a8c8aabace4b65d6503670ba2ba43%5E%21 Revert "tdf#49684 Don't focus on Navigator or Sidebar on show" It will be available in 6.2.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
@Jim -- maybe you have resolved this, but did change the status because you were waiting for someone (Cor?) to test? In relation to the two issues in comment 18 (nr. 1 is still the same, and for nr. 2, the focus shifts to Navigator when opened from a document, which is what I think was wanted.) Could not test all the variations you described in comment 19. Tested with: Version: 7.0.0.0.alpha0+ (x64) Build ID: cf96cb11e2a46c452a273ded1c66c556118983cf CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: threaded
(In reply to sdc.blanco from comment #23) > @Jim -- maybe you have resolved this, but did change the status because you > were waiting for someone (Cor?) to test? In relation to the two issues in Thanks - a bit busy, but.. tested in Version: 7.0.0.0.alpha0+ Build ID: fe75ce648c53e641048fe1fcd416868b784860e5 CPU threads: 8; OS: Linux 5.3; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-02-12_04:56:37 Locale: nl-NL (en_US.UTF-8); UI-Language: en-US Calc: threaded and indeed works nice now. Thanks Jim :) !!