Bug 140699 - Inserting a new line above or beyond a line with merged cells don't copy the merged cells
Summary: Inserting a new line above or beyond a line with merged cells don't copy the ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.4.7.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Cell-Add-Delete
  Show dependency treegraph
 
Reported: 2021-02-27 13:01 UTC by Harald Langheinrich
Modified: 2025-05-13 03:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Harald Langheinrich 2021-02-27 13:01:31 UTC
Description:
The information that cells are united goes lost.

example B20 and C20 are united and have one frame around them 
D20 has a single frame E20and F20 are united and have one frame around them 
I mark line 20  and insert new line above

B19, C19,D19,E19;F19 have all separate frames around B19:C19 and E19:F19 is not inited



Steps to Reproduce:
1.amke an example as describeld above with united cells and frames around
2.with copy paste make several lines ( this works as expected)
3.then select a line in the center and make insertnewline 

Actual Results:
separates cells 

Expected Results:
same result like copy and paste does, but in a new line eg. to enlarge a table 


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
[Information automatically included from LibreOffice]
Locale: de
Module: SpreadsheetDocument
[Information guessed from browser]
OS: Linux (All)
OS is 64bit: yes
Comment 1 m_a_riosv 2021-02-27 14:11:25 UTC
I think they are called merged cells.

Confirmed
Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: c5b911b23f45ba86100c2eadc747b27c8744a96d
CPU threads: 4; OS: Windows 10.0 Build 21296; UI render: Skia/Vulkan; VCL: win
Locale: es-ES (es_ES); UI: en-US Calc: CL

Version: 6.4.7.2 (x64)
Build ID: 639b8ac485750d5696d7590a72ef1b496725cfb5
CPU threads: 4; OS: Windows 10.0 Build 21296; UI render: default; VCL: win; 
Locale: es-ES (es_ES); UI-Language: en-US Calc: CL
Comment 2 Harald Langheinrich 2021-02-27 14:27:28 UTC
Thanks for correction 
.. the old babylon problem, if you are using another language 
I hope the problem is clearly stated
Comment 3 QA Administrators 2023-02-28 03:19:53 UTC Comment hidden (obsolete)
Comment 4 BogdanB 2023-05-13 12:01:23 UTC
You can select and copy B20:F20, and paste it in C21:F21, and it is working.
Comment 5 QA Administrators 2025-05-13 03:11:16 UTC
Dear Harald Langheinrich,

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