Description: In Calc, I often use text in cells, with "line returns" (Shift + Return). I can copy and paste a whole cell, and nothing changes, it's all good. Within a cell, when I highlight a portion of text that contains a Line Return, and paste that into another cell, the line return disappears, and I end up with just one big line. So I have to insert all the Line Returns again... (sorry, no idea about what Hardware it is) Steps to Reproduce: 1.In a cell, type words in the input line, Press Shift + Return, type more words. You should end up with two lines of text. 2. In the input line, Highlight and Copy the following: highlight some words (or everything) in the first line,continue through the Shift + Return, and include some words (or everything) in the 2nd line. And Copy. 3. Choose another cell, click on the input line, and Paste. Actual Results: You should see that the two lines have pasted as one whole line. Expected Results: This is not what I want to see, I want to see the two lines pasted as per the original copied section with the line return intact. Reproducible: Always User Profile Reset: No Additional Info: I can copy a whole cell, and paste it into another cell, and it works fine. This only happens when I copy within the input line above the spreadsheet.
It happens on the input bar. But if you do it, editing on the destination cell (no in the input bar) it works fine for me. I'm not sure if it is really a bug, but pasting on input bar always past without format. What does editing in the cell does.
I can confirm Selecting text from the formular bar, copying, clicking another cell, clicking the formular bar, pasting -> Line breaks removed, space inserted instead Setting OS to all in case this is not macOS limited Version: 7.5.1.2 (AARCH64) / LibreOffice Community Build ID: fcbaee479e84c6cd81291587d2ee68cba099e129 CPU threads: 10; OS: Mac OS X 13.2.1; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear TomS, 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