Bug 138711 - Frame disconnect after dragging down (comment 4)
Summary: Frame disconnect after dragging down (comment 4)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisectRequest, regression
Depends on:
Blocks: Shape-Textbox
  Show dependency treegraph
 
Reported: 2020-12-07 11:30 UTC by Telesto
Modified: 2023-04-24 03:24 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (32.11 KB, application/vnd.oasis.opendocument.text)
2020-12-07 11:30 UTC, Telesto
Details
Example file (33.01 KB, application/vnd.oasis.opendocument.text)
2020-12-08 19:40 UTC, Telesto
Details
The original document in Writer after pulling the second frame a bit right (121.85 KB, image/png)
2021-02-08 11:59 UTC, NISZ LibreOffice Team
Details
Screencast (257.58 KB, video/mp4)
2021-02-08 14:43 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-12-07 11:30:28 UTC
Description:
Text frame vanishes (becoming transparent) after dragging

Steps to Reproduce:
1. open the attached file (based on bug 138694 )
2. Scroll to page 2
3. Drag the left column frame to the right

Actual Results:
Disappears

Expected Results:
Not so


Reproducible: Always


User Profile Reset: No



Additional Info:
Found in
Version: 7.2.0.0.alpha0+ (x64)
Build ID: 32fdb8eb3506bc8dcf013cc713fe8e5debceb940
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL

frame without background but text present with
Version: 6.4.0.0.beta1+ (x64)
Build ID: 20be5cd0bdc57d812bf34a2debfe48caa51de881
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: GL; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Telesto 2020-12-07 11:30:42 UTC
Created attachment 167899 [details]
Example file
Comment 2 Xisco Faulí 2020-12-07 16:24:10 UTC
the issue is reproducible at times. Please provide a simplifier sample document where the problem is always reproducible
Comment 3 Telesto 2020-12-08 19:40:01 UTC
Created attachment 167990 [details]
Example file

1. Go to page 2
2. Select the outer frame (NOT the inner white line)
3. Drag it down slightly above the bottom page margin (frame splits)
4. Drag frame a additional time
5. Press Undo -> Undo fails (requires step 4)
Comment 4 Telesto 2020-12-08 19:53:42 UTC
(In reply to Telesto from comment #3)
> Created attachment 167990 [details]
> Example file
> 
> 1. Go to page 2
> 2. Select the outer frame (NOT the inner white line)
> 3. Drag it down slightly above the bottom page margin (frame splits)
> 4. Drag frame a additional time
> 5. Press Undo -> Undo fails (requires step 4)

Not sure if comment 0 being the exactly the same.. Anyhow above (comment 3) are also in 

Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

but less apparent (positions do different but not same extend) and undo actually working which big + compared to the current condition
Comment 5 Telesto 2020-12-08 19:56:28 UTC
The connection being perfect in
Versie: 4.2.0.4 
Build ID: 05dceb5d363845f2cf968344d7adab8dcfb2ba71

Bit snappy to the left border (like snap window to corner effect), but frames a perfectly synchronized
Comment 6 Telesto 2020-12-08 20:03:12 UTC
Possibly a duplicate.. bibisect will tell (or people are already working on it)

Adding NISZ as this kind of their specialty currently
Comment 7 NISZ LibreOffice Team 2021-02-08 11:59:37 UTC
Created attachment 169583 [details]
The original document in Writer after pulling the second frame a bit right

No longer reproduced in:

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 44b914b1e2616ca8f70e896e653a46ca93610234
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-GB
Calc: CL

But still present in slightly older bibisect-7.2:
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 380ab85b6594a013f34f5e6ec69fb569336bbb48
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL

I suspect the fix to bug #136516 solved this one.
Comment 8 Telesto 2021-02-08 13:13:44 UTC
@NISZ
Lazy me recycling this bug report. Comment 4 still broken
Comment 9 Xisco Faulí 2021-02-08 14:10:12 UTC
(In reply to Xisco Faulí from comment #2)
> the issue is reproducible at times. Please provide a simplifier sample
> document where the problem is always reproducible

Then putting to NEEDINFO until a simplified document is provided....
Comment 10 Telesto 2021-02-08 14:43:06 UTC
Created attachment 169589 [details]
Screencast

(In reply to Xisco Faulí from comment #9)
> (In reply to Xisco Faulí from comment #2)
> > the issue is reproducible at times. Please provide a simplifier sample
> > document where the problem is always reproducible
> 
> Then putting to NEEDINFO until a simplified document is provided....

Comment 4 is proper.. but here you go, a screencast
Comment 11 QA Administrators 2021-02-09 05:09:50 UTC Comment hidden (obsolete)
Comment 12 NISZ LibreOffice Team 2021-02-09 09:31:15 UTC
I see the split by moving the textbox one paragraph lower with attachment #167990 [details] in:

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 44b914b1e2616ca8f70e896e653a46ca93610234
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: en-US (hu_HU); UI: en-GB
Calc: CL

Not with the other attachment.
Comment 13 NISZ LibreOffice Team 2021-04-23 13:20:40 UTC
Still happens with:

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: db1cf111666847ce5ce93d18ae5ae8c29a4c44d6
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: threaded

Now in both example files the textboxes can be pulled by a few cm to the right and below to have their content and frame separated.

Also changing meta bug, these are odt files.
Comment 14 QA Administrators 2023-04-24 03:24:40 UTC
Dear Telesto,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug