Bug 35956 - Problem with data grids in occulted text sections
Summary: Problem with data grids in occulted text sections
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.2 release
Hardware: Other Windows (All)
: medium critical
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 07:57 UTC by Douglas Ricardo Boardman dos Reis
Modified: 2012-08-31 10:07 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
Open this Base Doc with LibreOffice 3.3.X, and then open the Form "Names" to see this problem occur. (13.17 KB, application/vnd.sun.xml.base)
2011-04-04 07:57 UTC, Douglas Ricardo Boardman dos Reis
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Ricardo Boardman dos Reis 2011-04-04 07:57:40 UTC
Created attachment 45223 [details]
Open this Base Doc with LibreOffice 3.3.X, and then open the Form "Names" to see this problem occur.

The problem occurs when the mouse cursor is moved thru occulted text sections containing data grids on OpenOffice Base Forms. Althought this sections are still occulted, when the mouse cursor is moved over the limits of this sections, those data grids started to be shown unexpectedly.
Comment 1 guilfordstuff 2011-05-16 05:31:15 UTC
If you insert a section with two columns, no auto-width, no auto-distribution of text, you can work with the first column but it's not possible to select the second column to enter text (unless you've changed what WYSIWYG means).  However, if you allow text to be auto-distributed between columns, the second column is accessible.
Comment 2 Björn Michaelsen 2011-12-23 11:51:55 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 Florian Reisinger 2012-08-14 14:03:46 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 4 Florian Reisinger 2012-08-14 14:04:41 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 5 Florian Reisinger 2012-08-14 14:09:10 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 6 Florian Reisinger 2012-08-14 14:11:11 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian