Bug 39125

Summary: UI: Drawings sent to background sometimes render on-screen in foreground
Product: LibreOffice Reporter: freedesktop-1092885
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: barta, freedesktop-1092885
Priority: medium    
Version: 3.4.1 release   
Hardware: x86-64 (AMD64)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: Step 11
Example document

Description freedesktop-1092885 2011-07-10 21:18:19 UTC
Created attachment 48949 [details]
Step 11

After using the drawing toolbar to create a basic shape (e.g., an ellipse) and then sending that shape to background using the context menu, the drawing will sometimes appear on top of text after scrolling with the mouse scroll wheel.

There was one occasion during my attempts to resolve the problem in which I thought a PDF exported from the document also contained the improper render order, but I have not been able to reproduce that and am no longer sure I remember it accurately.

The occurrence of the problem seems somewhat random, but I can reproduce it quickly with the following steps:

1. Create a new text document.

2. Set the font to Arial Black, 20pt.

3. Press the Enter key until you are near the bottom of the first page.

4. Type the word Test near the bottom of the first page.

5. Press the Enter key until you have a second page.

6. Use the ellipse tool from the drawing toolbar to cover the first part of the word Test with an ellipse.

7. Right-click the ellipse and select Arrange > To Background.

8. Scroll the document to the second page using the mouse wheel until none of the first page is visible.

9. Scroll upward using the mouse wheel until the word Test is visible.

10. Steps 8 and 9 may have to be repeated a couple of times; my testing seems to show the error about 50% of the time.

11. Right-click the ellipse and look under Arrange to see that the option To Foreground is available, demonstrating that the image is still "in the background" (although displaying in the foreground).


A screenshot showing step 11 is attached.

Assuming not too much time is required, I should be able to do any other things needed to assist someone in gathering more information to fix the problem.

Thank you.
Comment 1 freedesktop-1092885 2011-07-11 21:02:22 UTC
Created attachment 48992 [details]
Example document

Example file created using the steps in my prior comment
Comment 2 Björn Michaelsen 2011-12-23 12:25:00 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 3 freedesktop-1092885 2011-12-23 20:14:24 UTC
Bug persists in following version:

LOdev 3.5.0beta2 
Build ID: 8589e48-760cc4d-f39cf3d-1b2857e-60db978

Thanks.
Comment 4 freedesktop-1092885 2012-06-13 18:34:18 UTC
Still able to reproduce intermittently in following version:

LOdev 3.6.0beta1
Build ID: 1f1cdd8

Behavior not seen before is that any page redraw (not including menus or toolbars) will cause the display order to correct itself. For instance, moving the mouse across the document body/header boundary, which makes the header add button and border appear, will suddenly fix the problem and the layers will appear correctly.
Comment 5 ign_christian 2013-09-18 05:03:28 UTC
Hello.. Is that problem still reproducible in latest stable release? Always?

We'll set status to UNCONFIRMED waiting for someone (other than reporter) confirming your reported problem.
Comment 6 Chris 2013-09-26 00:35:25 UTC
I was not able to reproduce this bug. But possibly the bug still exists, as the reporter told it would show the error only sometimes.
Comment 7 Chris 2013-09-26 00:36:10 UTC
PS: Forgot to tell my Version: 4.0.5.2
Comment 8 tommy27 2013-11-13 18:12:58 UTC
I change status to NEEDINFO waiting 4 reporter feedback

is the bug still round here with current 4.1.x releases?
Comment 9 QA Administrators 2014-06-01 21:30:40 UTC
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
Comment 10 QA Administrators 2014-07-08 17:18:25 UTC
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