Description: This is a rebash of bug 105164. Pasting of unformatted text into an area with direct formatting, will result in applying the direct formatting to the pasted text. When pasting a single paragraph it's quite acceptable. However, the behavior will be unexpected and counter-intuitive when pasting multiple paragraphs, because only the last paragraph gets formatted. There are lots of easy workarounds, but the behavior looks quite odd when pasting multiple paragraphs. Steps to Reproduce: 1. Copy text between the dashes into a new Writer document ---- ABC DEF GHI JKL MNO DEF GHI KLM NOP QRS TUV WXY ---- 2. Note that everything is pasted without direct formatting (Font Color: Automatic) 3. Select ABC (apply some direct formatting; bold/underline/Highlight/Font Color) 4. Set the cursor after the 'C' and hit enter (creating a new paragraph; which has the same formatting as ABC. Note: it can happen by accident). 5. Cut/paste or drag "DEF-WXY" into the paragraph created in step 3. 6. WXY will be formatted to the applied formatting of the paragraph below ABC. The rest will be black without direct formatting (Font Color: Automatic) As an alternative I have added test file. With two paragraphs with different formatting. Actual Results: WXY will be formatted to the applied formatting of the paragraph below ABC. The rest will be black without direct formatting (and font color: Automatic) Expected Results: As steve -_- already commented in bug 105164#c11: only adapting to the formatting for the last row unexpected and counter-intuitive. Three possible solutions: 1. Not the last but the first paragraph should be formatted (problem and source are nearby) 2. All text dragged into a certain formatted paragraph should adapt to the formatting 2. No formatting should be applied Personally I prefer the last one, because it's quite common behavior in most text editors. - MS Word - Wordpad - Mozilla Thunderbird - Zotero - Google Docs - Mac Texteditor - Pages - Abiword Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 5.4.0.0.alpha0+ Build ID: 99eed82939999d9a9689788a4134dd05d5c20c5a CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-01-14_23:37:40 Locale: nl-NL (nl_NL); Calc: CL and in LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
Setting to NEW. Confirmation: https://bugs.documentfoundation.org/show_bug.cgi?id=105164#c11 --> let's bring this to the attention of the design team
(In reply to Telesto from comment #0) > Expected Results: > 1. Not the last but the first paragraph should be formatted (problem and > source are nearby) > 2. All text dragged into a certain formatted paragraph should adapt to the > formatting > 3. No formatting should be applied Definitely yes to 3. We also aim to promote formatting by styles and the direct formatting shouldn't "made easy". As a rule of thumb direct formatting must not be applied or inherited automatically. Guess we can remove UX safely.
It's a little bit more difficult: when you paste the paragraphs *ABC|DEF* within the bold word (at the pipe sign) you expect the first and last line to be formatted in bold and everything else taking what is defined in the source => WFM. When you paste at *|ABC* it should be the same and similarly when there is no text at all. Assuming we do no formatting it becomes *1 2 3* ABC (removing the bold formatting from *ABC*) So after all I'm for closing this ticket as WFM.
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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 131104 has been marked as a duplicate of this bug. ***
Repro 7.0+ with ODT attachment 158393 [details] from bug 131104, seen as attachment 158355 [details]. Note: select just 2 paragraphs with text to be seen (or empty 3rd will be bold).
The status of the bug, which apparently was a duplicate, has been changed to resolved. I'm uncertain about what that means. Will something change in upcoming LibreOffice updates, or do we just continue to work around this?
(In reply to Randy from comment #7) > The status of the bug... Right ticket? This issue is still open, we did just some housekeeping today.
My mistake. I misunderstood the email update I received.
*** Bug 116863 has been marked as a duplicate of this bug. ***
I added bug 126737 to See Also because that report is mostly about this bug. But I kept it open for another smaller issue.
*** Bug 102505 has been marked as a duplicate of this bug. ***
*** Bug 97248 has been marked as a duplicate of this bug. ***
*** Bug 86271 has been marked as a duplicate of this bug. ***
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