Created attachment 63752 [details] The tab on top of the second page is wrong formatted Problem description: Wrong table format when the table is on top of page. The document is composed by program from a model. When the "conclusion" Tab (or another) is on the top of the page, the paragraph format of the table text is wrong. Platform (if different from the browser): Browser: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20100101 Firefox/14.0
Created attachment 63753 [details] The document when the tab is not on top of the page
Thanks for the bug report. However, could you please attach screenshots showing what is wrong and what is expected? Thanks again.
Created attachment 63874 [details] screenshots from what is expected and what is wrong
I add two documents. The first is the document as it should be. The second is a macro to display this document in preview mode. The problem is on the table on top of the second page of the document. The row height is not correct.
Created attachment 65072 [details] the document as it should be
Created attachment 65073 [details] the macro to open file in preview mode
Sorry for the trouble, dany. But still I don't understand. :( Could you please answer the followings: - Which attachment has a problem? attachment 63752 [details] in comment 0? Other attachments don't have problem, right? - Is the problem for spacing located below or above the word "CONCLUSION"? or both? - From the screenshot, what it should be is the word "CONCLUSION" is in page 1. So, the bug is that it is in page 2, right? - Are you using same version of LibreOffice for creating screenshots? I mean, is this bug newly occurred with 3.6.x version but not 3.5.x? or it already occurred with 3.5.x? or you didn't test this? Also, in the screenshot, could you please points, circles, or marks the problem? and then upload it again. Last, I changed the version field back to 3.6.0.0.beta2 because it should be the earliest version with problem. Thanks and sorry again. For others if you are reading this, the steps are: 1. Download attachment 63752 [details] and save as D:\temp001.odt 2. Start LibO 3. Tools > Macros.. > Organize Macros > LibO Basic 4. Click Edit button on the right-hand side 5. Copy the content in attachment 65073 [details] to replace all codes in the window 6. Press <F5> on the keyboard. The document should be shown. Note that you might modify the line > adressedoc=convertToUrl("d:\temp001.odt") to path/to/your/file accordingly.
- Which attachment has a problem? attachment 63752 [details] in comment 0? Other attachments don't have problem, right? The attachment 63752 [details] is correct, but if you open it in preview mode you can see that on the top of the second page the spacing below "Commentaires particuliers" is wrong - Is the problem for spacing located below or above the word "CONCLUSION"? or both? as you can see on attachment 63874 [details], the problem in on the top of the second page below the word "Conclusion". On attachment 63752 [details] it's below "commentaires particuliers" - From the screenshot, what it should be is the word "CONCLUSION" is in page 1. So, the bug is that it is in page 2, right? The screenshot represents the normal height of the cells below "Conclusion" and the wrong height of these cells when the tab begins on a new page. "Conclusion" or "Commentaires particuliers" are the first cell of the tab. - Are you using same version of LibreOffice for creating screenshots? I mean, is this bug newly occurred with 3.6.x version but not 3.5.x? or it already occurred with 3.5.x? or you didn't test this? I tried it today under Linux with version 3.5.5.3 (attachment 63752 [details] and the macro) and I have the same problem. But it never occurs on version 3.3.
Created attachment 65147 [details] more details
I'm just looking for unconfirmed bugs: Downloaded https://bugs.freedesktop.org/attachment.cgi?id=63752, saw the wrong height of the two rows of the table of the second page. Then I tried to reproduce it with a new Writer-document. I couldn't. Created a document, created text and a table, set return so the table went at the top of the next page - formatted right. Then I opened the attached document again. Set the cursor after "Conclusion", input a space and the two rows will turn to the height you expected. This is the same behavior with any LO-version I have tested (LO 3.3.4, LO 3.6.7.2 and LO 4.1.1.2) How did you create this document? For a bug-description the problem must be isolated as good as possible. When you say it is an incorrect table-format of every table, which appears at the top of a page there must be a document, which only shows this behavior. When it appears only for one special document I would say the document is defect. Let us repair this and close the bug.
>How did you create this document? The document was created with DCom under Windows. We have thousands of these documents in a year, but some of them have this problem. >For a bug-description the problem must be isolated as good as possible. When >you say it is an incorrect table-format of every table, which appears at the >top of a page there must be a document, which only shows this behavior. I never said that the problem appeared with every table on top of page. The only common element I see was that the table was on top of page, but it was not sufficient to generate the bug. >When it appears only for one special document I would say the document is >defect. Let us repair this and close the bug. The document is based on a model. You think that the model has a problem. But how explain that only the preview mode generate the bug ? The same documemt, when printed, is normal.
Dany, this is a hell of confusing bug. It's got separate info all scattered around. Ton of attachments and 11 comments. I open the test document I look at print preview and can't spot any difference. Can you please post a screenshot that clearly indicats the glitch we are looking for? Is this bug still valid / reproducible with the latest pre-release 4.2.0.1: http://www.libreoffice.org/download/pre-releases/ Should this be still reproducible for you with the latest LO release please set this bug back to UNCONFIRMED. Should this issue be solved set it to WORKSFORME. Setting to NEEDINFO until more detail is provided. Also from what you write this could well be NOTOURBUG. If odd documents get created by third party software, maybe there's the culprit of this bug?
The problem is not in the print preview but in the preview mode (no modification possible because no active menu). This mode is (perhaps) only usable with a macro such as described in the 5th attachment.
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of FDO