Description: Когда поле (Вставка - Поле - Ещё поля) в шаблоне заполняется слишком большой информацией, то часть текста должна оставаться на частично заполненной первой странице, а другая переходить на другую, но на деле получается, что весь текст начинается со второй страницы. //------- When the field (insert - field - more fields) in the template is filled with too much information, then part of the text should remain on the partially filled first page, and the other should move on to another, but in fact it turns out that all the text starts from the second page. Steps to Reproduce: 1. Create new document 2. Insert fields 3. Fill document from another programm and insert into the field with more text (~ 1 page full) Actual Results: All the text starts from the second page Expected Results: Part of the text should remain on the partially filled first page, and the other should move on to another Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Версия: 6.1.2.1 (x64) ID сборки: 65905a128db06ba48db947242809d14d3f9a93fe Потоков ЦП: 4; ОС:Windows 10.0; Отрисовка ИП: GL; Локаль: ru-RU (ru_RU); Calc: CL
Created attachment 146253 [details] fields
I confirm this behaviour with Version: 6.2.0.0.alpha1+ (x64) Build ID: 8274c4c62df5b937b3f0bec9e1eeca85f3b219d4 CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-10-22_01:47:50 Locale: en-US (de_DE); Calc: CL Further observation: If you disable "Orphan Control" and "Widow Control" (Format => Paragraph => Text Flow) it works.
Also reproduced in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a) LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4
Dear bookashechka, 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
Still present in Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: en-GB Calc: CL