LibreOffice has a terrific feature that lets one add a horizontal line by placing four dashes in a new paragraph. However, it is not clear to the user that the horizontal line is actually a border to the preceding paragraph, rather (due to the manner in which it is added) it is perceived as being an entity all its own. Therefore it is not clear to the user how to remove it. Users try to backspace over the "entity" that is the horizontal line, and this of course does not work. Sometimes users try to highlight it and then press Enter, which results in a _second_ horizontal line appearing! Please devise an intuitive way to remove this horizontal line. I can make suggestions based on what users try to do to the line to remove it.
oh, wasn't aware of this funny feature. but "Undo" seems to be simple enough to me?
looks more like "enhancement" to me in any case.
@Michael Stahl: Undo is fitting for removing the paragraph border directly after it is made. Undo is not fitting for trying to remove it later.
Hi Dotan, Michael, thanks for bringing this to my attention... I've been in the situation of wanting to remove such a line a couple times already. I didn't know the explanation so far. So yes, I fully agree with Dotan that this behaviour is terrible. Undo usually didn't help me (much) when I was in the situation, since usually I'd written more text in the meantime which I didn't want to delete. Maybe there is a way of creating a "real," drawing line automatically that is anchored to the bottom of the paragraph instead? The only problem I see with that is that this might make it too easy to move/delete the line... but that seems minor.
I found this "feature" by accident while typing an assignment very important to me. Writer kept adding lines every time I pressed the enter key, even after typing characters. Once enabled there is no apparent way to disable this "feature". This is a deal breaker for me. To complete my assignment I had to install Abiword.
*** Bug 40930 has been marked as a duplicate of this bug. ***
Instead of adding yet another interface to change formatting, one could simply fix this "feature-bug" by deactivating the corresponding autocorrection option by default. Why not make the quick formatting (horizontal rule, *italics*, _underlined_) an opt-in instead of an opt-out?
*** Bug 56912 has been marked as a duplicate of this bug. ***
Rephrased the summary so that people searching for "ruler" can find this bug report.
Hi! Thank you for filing this bug report. I've always considered this a fatal disease a document can catch from a couple of dashes being typed in consequence. This is SO annoying. I've been experiencing this for YEARS and the only two remedies I've discovered are 1) undo (losing all text typed afterwards) 2) save as plain text and reopen (losing all formatting in the document) My suggestion: I think the feature would be actually really useful, if the line was an object of the same type as a hard page break - something you insert as a character and can delete later on as a character. This paragraph-border implementation is way too cryptic for me. Dude, I hadn't figured it out until I read it in this bug report today!
Work around (or solution - depending how you look at it): - Select parapragh or Put cursor in paragraph - choose Format > Clear direct formatting (or Ctrl+M) - or got to Format > Paragraph and remove the line on the tab Boarder
thanks Cor, I'll keep in mind that workaround. anyway IMHO a more intuitive way to remove those lines is needed expecially for newbies.
I don't think it's a bug: people attempting to use professional tools as office suites are expected to learn them first. There are plenty of other text editors like Scrivener for household users.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.0.0.5 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
situation is the same in recent versions.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.5 or 5.2.1 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Still reproducible. Version: 6.2.0.0.alpha1+ Build ID: 0378bfcea51ff0f379d0954aa6740f1829909dc3 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: threaded
*** Bug 125833 has been marked as a duplicate of this bug. ***
Seth Chaiklin committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/help/commit/a14906302a559fdd49efdd22444dea1643924fda Relevant to: tdf#45721 add tip about removing "Apply borders"
Dear Dotan Cohen, 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