Created attachment 91457 [details] Test case showing the problem Problem description: Steps to reproduce: 1. Create a variable in the header 2. Create new line, show variable in 2nd line 3. Move varibale to 1st line Current behavior: Variable disappears Expected behavior: Variable shown. Please see attached document with the behaviour. When the 1st (empty) line is deleted, the variable disappears. Tried in 3.5.5.2 and 4.1.3.2 Operating System: Ubuntu Version: 4.1.3.2 release
I can confirm that the described behaviour is the same on Windows 7 with LibreOffice 4.1.4.2 with the provided document. If I perform the steps in a new document with a variable of the 'standard' type, I get the expected behaviour, i.e. the variable does not disappear.
Hi. After investigations under LibO 4.2.0.1 rc1 on Win 7, I found the following : After deleting first (empty) line, the variable doesn't disappear, instead its value is changed to blank. The questions turns to be "when is this variable's value set ?" : it is in the "field/other/set variable", in the header. So I suppose that the header is processed at the first paragraph mark of the page (= evidence of a non-empty page), and not at the very beginning of the page body. I consider that the documentation should be more explicit on the sequence of setting/showing of such a variable (a text is not a program ; the use of variable, for instance to command the hiding of pieces of texts, is not intuitive).
I recently thought to another reason for which the header is processed at the first paragraph mark of the page : it could be to avoid that the header's composents be in the middle of a component of the body text, in case it begun in the previous page.
Confirmed, the variable content is reset when the first line is deleted, ctrl+F9 displays the field correctly, F9 doesn't update it. Tested under Version: 4.2.3.2 Build ID: 7c5c769e412afd32da4d946d2cb0c8b0674e95e0 Ubuntu 13.10 Set as New - Sophie
** 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.1 or preferably 5.0.2.2 or later) 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: 2015-10-14
Still confirmed. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: a7c3a2a9be83686657c06f37d521f9f6d2004ddd Threads 4; Ver: Windows 6.1; Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2015-11-28_04:39:18 Locale: fi-FI (fi_FI)
** 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
don't repro in Версия: 6.2.1.1 ID сборки: 757c58e8cb70b2982843211a54750fb3cd79acd5 Потоков ЦП: 4; ОС:Windows 6.1; Отрисовка ИП: по умолчанию; VCL: win; Локаль: ru-RU (ru_RU); Язык UI: ru-RU Calc: threaded Status->WFM