Bug 51420 - VIEWING: Some Form Controls Become Invisible if Cursor is Moved in Front of Heading Number
Summary: VIEWING: Some Form Controls Become Invisible if Cursor is Moved in Front of H...
Status: RESOLVED DUPLICATE of bug 43765
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.3.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
Whiteboard: BSA
Depends on:
Reported: 2012-06-25 12:18 UTC by Harald Koester
Modified: 2013-06-24 18:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

test case with description inside (12.55 KB, application/vnd.oasis.opendocument.text)
2012-06-26 01:28 UTC, sasha.libreoffice

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Koester 2012-06-25 12:18:34 UTC
Problem description: 

(1) Open new text document.
(2) Insert a heading with level 1.
(3) Number the heading: Tools > Outline Numbering... > Numbering > Level 1 > Number: 1, 2, 3,…; then OK. 
(4) Insert a check box below heading.
(5) Set design mode to "off".
(6) Move the cursor with arrow buttons in front of the heading number. The check box becomes invisible !!!
(7) Pull the document up and down with mouse wheel. The check box becomes visible again.

Expected behavior: In step (5) the check box should be still visible.

Also Option Buttons and Label Fields become invisible with this proceeding. But not all form controls disappear, Push Buttons and Text Boxes are still visible.

Hence this bug is similar to bug 43765, there may be the same cause for this bug.
Browser: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20100101 Firefox/13.0.1
Comment 1 sasha.libreoffice 2012-06-26 01:28:07 UTC
Created attachment 63477 [details]
test case with description inside
Comment 2 sasha.libreoffice 2012-06-26 01:29:34 UTC
Thanks for bugreport
reproduced in 3.3.4, 3.5.4, 3.6.b1 on Fedora 64 bit

Changing version to 3.3.4 as most early reproduced
Comment 3 Michael Stahl (allotropia) 2013-06-24 18:27:05 UTC

*** This bug has been marked as a duplicate of bug 43765 ***