Created attachment 106627 [details] File just before the issue If I change the condition on a conditional text field, this causes a hidden section to unhide. Steps: 1. Create a new document 2. Insert variable varA with value "is" (without the quotes) -- a. Insert > Fields > Other > Variables > Set Variable -- b. Name: varA -- c. Value: is -- d. Click Insert 2. Press enter 3. Insert variable varB with value "is" (without the quotes) -- same as step 1 with name varB 4. Press enter 5. Insert a conditional field based on varA -- a. Insert > Fields > Other > Functions > Conditional Text -- b. Condition: varA EQ "is" (with the quotes) -- c. Then: Ais -- d. Else: AisNot -- e. Click OK 6. Press enter 7. Insert two section based on varB -- a. Type "Hide this section if varB is" (without the quotes) -- b. Press enter -- c. Type "Hide this section if varB is not" (ditto) -- d. Select the first of the two lines -- e. Insert > Section -- f. Check Hide -- g. Condition: varB EQ "is" -- h. Select the second of the two lines -- i. Insert > Section -- j. Check Hide -- k. Condition: varB NEQ "is" Attachment is at this point. 8. Double-click "Ais" 9. Change condition from EQ to NEQ 10. Click OK Actual result: Hidden section appears Expected result: No change to which section is hidden and which isn't Actually 4.2.6.3 but that's not offered in the dropdown at time of filing. Hardware is Intel Core 2 Duo
Not sure why you entered this bug twice ? *** This bug has been marked as a duplicate of bug 84144 ***
It's not actually intended as a duplicate. While the creation steps are nearly identical, the other bug (84144) involved a single variable showing two section opposite to their expected true and false state. On the other hand, this bug (84148) involves two unrelated variables, in which making a change to one variable impacts a section that is only supposed to be affected by the unrelated variable. I'm removing the duplicate. That said, if the two different behaviors are caused by the same code and therefore you feel it really is a duplicate, please go ahead and re-close, but also copy the symptom over to the other bug.
OK sure, I guess it will takesomeone with a debug build to unwind this.
I have linked the two reports instead of calling one a duplicate of the other until it can be investigated in more detail.
Moving to UNCONFIRMED as this has not been confirmed by a QA team member.
Confirmed on Version: 4.3.3.1 Build ID: 7d55112667c8fcddb67bc3803796b46c93aa56b0
** 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.1.6 or 5.2.3 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-20170103
Still present in 5.2.6.2, Windows 10 /x64.
Created attachment 132981 [details] Test document for 84148 with buggy variable evaluation From LO Writer 5.2.6.2 under Win10/x64. Bug 84146 is evident when setting VarA and VarB, but 84148 with updated behavior happens with the conditional text at the end (changing EQ to NEQ doesn't change result) followed by two sections both showing but with opposite conditions to hide.
Still present, and was also present in 3.3.0 so inherited from OOo Also a Windows issue, so setting OS to all Version: 6.0.0.0.alpha1+ Build ID: 7e03c4eed72452fdfb87341214a21956c08ba969 CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2017-10-25_23:45:02 Locale: en-US (en_US.UTF-8); Calc: group Version: 5.4.0.3 (x64) Build ID: 7556cbc6811c9d992f4064ab9287069087d7f62c CPU threads: 1; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
** 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
Steps changed slightly in LibreOffice 6.0.7.3: Steps: 1. Create a new document 2. Insert variable varA with value "is" (without the quotes) -- a. Insert > Field > More Fields > Variables > Set Variable -- b. Name: varA -- c. Value: is -- d. Click Insert 2. Press enter 3. Insert variable varB with value "is" (without the quotes) -- same as step 1 with name varB 4. Press enter 5. Insert a conditional field based on varA -- a. Insert > Field > More Fields > Functions > Conditional Text -- b. Condition: varA EQ "is" (with the quotes) -- c. Then: Ais -- d. Else: AisNot -- e. Click OK 6. Press enter 7. Insert two section based on varB -- a. Type "Hide this section if varB is" (without the quotes) -- b. Press enter -- c. Type "Hide this section if varB is not" (ditto) -- d. Select the first of the two lines -- e. Insert > Section -- f. Check Hide -- g. Condition: varB EQ "is" -- h. Select the second of the two lines -- i. Insert > Section -- j. Check Hide -- k. Condition: varB NEQ "is" Attachment is at this point. 8. Double-click "Ais" 9. Change condition from EQ to NEQ 10. Click OK Actual result: Hidden section appears Expected result: No change to which section is hidden and which isn't Same actual result as the issue I originally posted. So, still an issue.
Created attachment 146535 [details] Retest of steps in LibreOffice version 6.0.7.3
From LibreOffice > About LibreOffice Version: 6.0.7.3 Build ID: dc89aa7a9eabfd848af146d5086077aeed2ae4a5 CPU threads: 4; OS: Mac OS X 10.13.6; UI render: default; Locale: en-US (en_US.UTF-8); Calc: group
Dear Chas Belov, 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
Can repro using STR in comment #12. Change the conditional function with varA and the section with varB becomes "unhidden" (even though the controls are still set) Version: 6.3.4.2 (x64) Build ID: 60da17e045e08f1793c57c00ba83cdfce946d0aa CPU threads: 8; OS: Windows 10.0; UI render: GL; VCL: win; Locale: da-DK (en_DK); UI-Language: en-US and Version: 6.5.0.0.alpha0+ (x64) Build ID: 035c7717c135c66c0ec025500b73ae9c13b7c586 CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: da-DK (en_DK); UI-Language: en-US Calc: threaded
IMO there's no "change in one field changes condition in another". Rather, there's "wrong and inconsistent work with conditions at all". To see this, don't modify any conditions, just use Tools->Update->Update All.
Dear Chas Belov, 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