In a form with the text box it is impossible to enter some text to it. (The only way I found to do it is to right mouse button click to that text box. Then it gets the focus and becomes editable). Steps to reproduce: 1. Create new drawing; 2. Switch on Design mode in Form Controls toolbox; 3. Create Text Box; 4. Switch off Design mode in Form Controls toolbox; 5. Try to enter some text to that Text Box.
Yep, I reproduce. 4.3 is ok. Win 7 Pro 64-bit Version: 5.1.0.0.alpha1+ Build ID: b216cc1b8096eb60c27f67e8c27b7cd756c75e38 TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2015-11-12_00:06:20 Locale: fi-FI (fi_FI) Version: 4.3.0.1 Build ID: 67f5430184326974072b65403ef1d9d934fc4481
bibisect-win32-5.0, oldest version contains bug too. git checkout oldest: Version: 4.5.0.0.alpha0+ Build ID: 57d6b92b69a31260dea0d84fcd1fc5866ada7adb
(In reply to Valery from comment #0) > 5. Try to enter some text to that Text Box. Right click is the trick :-)
This seems to have begun at the below commit. Adding Cc: to Marco Cecchetti ; Could you possibly take a look at this one? Thanks 4e9a26b54b5533353b8d56e813a02635d7efb21c is the first bad commit commit 4e9a26b54b5533353b8d56e813a02635d7efb21c Author: Matthew Francis <mjay.francis@gmail.com> Date: Sun Mar 15 05:10:04 2015 +0800 source-hash-967a386bccb15b99915a1e878e42450fbe9a2d0e commit 967a386bccb15b99915a1e878e42450fbe9a2d0e Author: Marco Cecchetti <mrcekets@gmail.com> AuthorDate: Wed Nov 5 20:15:32 2014 +0100 Commit: Marco Cecchetti <mrcekets@gmail.com> CommitDate: Wed Nov 5 20:21:43 2014 +0100 Fix for SUSE L3 bug 624546 (freedesktop 83733) Problem: When I'm in outline mode, if I select a slide in the left slide preview pane, ctrl-c, then select another slide I would like it after and hit ctrl-v; it refuses to cut/paste. Analysis: This issue is due to the fact that the outline view always grabs focus when activated and a view is activated whenever is pushed to the sfx shell stack even if it is not the new top-most active view shell (see `ViewShellManager`, `SfxViewShell`, `SfxDispacther`). Solution: Make the `OutlineViewShell` grabs focus only if it is the top-most active view shell. Rationale: When `OutlineViewShell::Activate` is invoked, instead of removing the focus grabbing action completely, we check if the `OutlineViewShell` instance is the the top-most view shell and perform the focus grabbing action only in such a case. This change required to have also the `DrawViewShell` grabbing focus on activation (only when it is the top-most view shell). In order to implement this solution I needed to add a new method (and data member) to the `ViewShellManager` class. I named it `GetTopViewShell`. This method returns a pointer to the top-most active view shell of the internal stack. The returned pointer is updated in the `UpdateShellStack` method, before the sfx shell stack is updated. For more details see : https://gist.github.com/mcecchetti/15b3ebc505d6582ea0db Change-Id: I619a406864f50f0e62dee3fcb9ac5d46e3d48272 bibisect-44max$ git bisect log # bad: [cf6ea17155fabb2a120ba07c150735591ac861d7] source-hash-3f94c9e9ddfd807b449f3bb9b232cf2041fa12d2 # good: [fc71ac001f16209654d15ef8c1c4018aa55769f5] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e git bisect start 'latest' 'oldest' # good: [8cf60cc706948588e2f33a6d98b7c55d454e362a] source-hash-f340f0454627939f1830826fb5cc53a90e6c62a4 git bisect good 8cf60cc706948588e2f33a6d98b7c55d454e362a # good: [8cf60cc706948588e2f33a6d98b7c55d454e362a] source-hash-f340f0454627939f1830826fb5cc53a90e6c62a4 git bisect good 8cf60cc706948588e2f33a6d98b7c55d454e362a # good: [7beddf3808dadd525d7e55c00a5a90a2b44c23d3] source-hash-2f10386ce577f52e139aa23d41bc787d8e0b4d59 git bisect good 7beddf3808dadd525d7e55c00a5a90a2b44c23d3 # good: [fb3ec529b3f37f0c7eab2e9b7a9cc695c0f27676] source-hash-0516d123f53917d1833c7e8a8c528a619c71a0af git bisect good fb3ec529b3f37f0c7eab2e9b7a9cc695c0f27676 # bad: [47a64818ddfe63bbb8e6448fcc476f55996d61b1] source-hash-d12efada389643ab0e13a280246d14caed273029 git bisect bad 47a64818ddfe63bbb8e6448fcc476f55996d61b1 # bad: [5ce59f880a90cf8134a9d765c2b94bc4f6f5a865] source-hash-e377a65a1e6acf6241ce0bd2fc35a6a786cd8de9 git bisect bad 5ce59f880a90cf8134a9d765c2b94bc4f6f5a865 # bad: [a568e53084f7d0a47b9e814b938f8deab225f7fc] source-hash-8cdcea2689600ef16829a3f951ddf6fb8e9125a0 git bisect bad a568e53084f7d0a47b9e814b938f8deab225f7fc # good: [3c987d7227c844df37802b80ccd8fec798dfe360] source-hash-6e4ee0c0f5b0e314ead2e87438e09eae513e5dc3 git bisect good 3c987d7227c844df37802b80ccd8fec798dfe360 # good: [87d7d87521fcc3acbe035d3a5e0a6bd74c96860e] source-hash-5e48dc03fe3dfb173fe65c46d52552149b255032 git bisect good 87d7d87521fcc3acbe035d3a5e0a6bd74c96860e # bad: [b153d5222738044cd6aa8b249c8371d28d92caca] source-hash-9632045906baf165076d11a97f45b153d8e2acb7 git bisect bad b153d5222738044cd6aa8b249c8371d28d92caca # good: [313358ad8c5d66d0424f67d133d7170e5a42c0e7] source-hash-ea272d9fe4bf2dc7419f76e2ddee707d768ccd50 git bisect good 313358ad8c5d66d0424f67d133d7170e5a42c0e7 # good: [f96b11ff77327e1f5c94937755fc41b8f4e1db04] source-hash-3943daaa353ca3cd4ae1873249c94ed2856dd99a git bisect good f96b11ff77327e1f5c94937755fc41b8f4e1db04 # good: [f9d49af44e00db3c5ebef0cdd8f272b22cc9b2d3] source-hash-33b5b467224fef8d99ba3f6f4cba3d404119c100 git bisect good f9d49af44e00db3c5ebef0cdd8f272b22cc9b2d3 # bad: [4e9a26b54b5533353b8d56e813a02635d7efb21c] source-hash-967a386bccb15b99915a1e878e42450fbe9a2d0e git bisect bad 4e9a26b54b5533353b8d56e813a02635d7efb21c # good: [65b5cc30bc812d9672a9d9c751af0dec390f165e] source-hash-a9a9718bb1f64318429562ecdaa3d3763d9e2f4a git bisect good 65b5cc30bc812d9672a9d9c751af0dec390f165e # first bad commit: [4e9a26b54b5533353b8d56e813a02635d7efb21c] source-hash-967a386bccb15b99915a1e878e42450fbe9a2d0e
Migrating Whiteboard tags to Keywords: (bibisected) [NinjaEdit]
** 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-20170929
Repro 6.2+.
*** Bug 120389 has been marked as a duplicate of this bug. ***
*** Bug 107206 has been marked as a duplicate of this bug. ***
Dear Valery, 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
Repro 7.1+
*** Bug 136862 has been marked as a duplicate of this bug. ***
Dear Valery, 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
repro 25.2+ For testing, I used "Form_ListBox_LO44.odg" (attachment 132609 [details]) from duplicate bug 107206. Sometimes I could see the flicker of the dropdown menu containing the selected word. So it appears as though on the mouse-down, the object is selected and acted on, but then the focus is lost. If I insert a text-box with some content and the cursor is in the textbox's text, and then click on the listbox, I can easily see the listbox start to activate, but then the focus changes back to the textbox - which becomes selected. As indicated in a duplicate bug, clicking on the slide in the "Page Panel" on the left allowed the first attempt to access the drop-down to work. Once it loses focus, it cannot gain it back again (until the focus leaves the slide). I was NOT able to use the right-click to gain access to the text (using Linux).
Heh - all this time and just three hours of debugging (in an area where I know nothing) provides a likely-soundsing fix of - mpTopViewShell = (maActiveViewShells.empty()) + mpTopViewShell = (maActiveViewShells.empty() || mbFormShellAboveParent)
Justin Luth committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/27f7770e3e9be60b0caef8469666474151a753fb tdf#95852 sd: not TopViewShell if mbFormShellAboveParent It will be available in 25.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.