Created attachment 122429 [details] "AUTOCORRECT" BUTTON Hi, I added the autocorrect icon in Libre Office tool-bar to increase conversion of text prom web to editor (using Autocorrection Option), but when clicking it nothing happen, and if I select text and press button, the text disappears, can anyone help ? Please ? Is "Autocorrect" like "Autocorrection" or should I use an other button ? Does it is available. Kanth you.
Reproduced. For me, it inserts a space when clicking. If something is selected, selection is replaced by space. Win 7 Pro 64-bit Version: 5.2.0.0.alpha0+ Build ID: a6f876d45bd4e41a7143594a6cb11b6893a0f620 CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-02-11_00:07:38 Locale: fi-FI (fi_FI)
@nemzag You have been filing a lot of these low quality bug reports recently. This adds noise to the bug tracker. You need to understand that all of the developers are volunteers, many of which have expressed their dislike of vague reports. Low quality reports discourage them from coming here. > Is "Autocorrect" like "Autocorrection" or should I use an other button ? > Does it is available? This is a bug track not a support forum. Use Ask LibreOffice for your support issues. You should never be filing a bug report about a feature that you don't understand. Before coming here, you should have gone to https://help.libreoffice.org/Writer/AutoCorrect You should only be filing bug reports for features that you have a clear understanding of how they should work. If you are confident you've truly found a bug, then your bug report should always have the following 3 components: Steps to Reproduce: Expected Results: Actual Results: So this bug report should have looked like this: Steps to Reproduce: 1. View->Toolbar->Customize 2. Toolbar -> Formatting 3. Toolbar Content -> Add 4. Add AutoCorrect 5. Highlight a word Expected Results: Do nothing to the document, but toggle AutoCorrect On/Off Actual Results: Highlighted text is replaced with a space We either need a better tooltip description of what the button does, remove it from list of toolbar buttons, or we need to make it toggle AutoCorrect On/Off.
OK
I'm only an user, not a professional, you should be glad, that I spend my time pro nothing, to report to you bugs, when I can spend this time with my family or else, or instead than using a stable tool like Microsoft Office, who don't crash and hang so much, and who is 5x faster in Calc/Excel and database... I'm not happy that some of you, threating me like this, when I only try to improve & suggest things you. I'm not a professional, and I don't all of wnow what you know, since the time that you are here. I'm a newbie. But if you are not happy then I will report any poly to you. Good day.
(In reply to nemzag from comment #4) > I'm only an user, not a professional, > you should be glad, that I spend my time pro nothing, > to report to you bugs, when I can spend this time with my family or else, or > instead than using a stable tool like Microsoft Office, who don't crash and > hang so much, and who is 5x faster in Calc/Excel and database... We are also doing this without compensation. We are in the same boat, so please don't sabotage the boat and refrain from such passive aggressive comments and stick to the topic.
I'm not saboting nothing, I only report.
** 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.2.5 or 5.3.0 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-20170306
Steps from Comment #2 still have same results. Version: 5.4.0.0.alpha0+ Build ID: 5b805de10a1b05647b616e726f0a8b88ff30ae77
** 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 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
Still reproducible with Version: 6.1.0.0.alpha0+ Build ID: adc6ba2ad502f095dde8f36242fda9aaa6c276fd CPU threads: 4; OS: Linux 4.13; UI render: default; VCL: gtk3; Locale: de-DE (de_DE.UTF-8); Calc: group Build from today
The command is .uno:StartAutoCorrect and it executes https://opengrok.libreoffice.org/xref/core/sw/source/uibase/shells/textsh1.cxx#779 (/* Autocorrect from Basic */ is the comment at the ID). Any idea where this command comes from, Maxim?
Removing UX as this issue is just a bug. Please fix it. (And I don't expect users to dig into the workflow to report an issue.)
(In reply to Heiko Tietze from comment #11) > The command is .uno:StartAutoCorrect and it executes > https://opengrok.libreoffice.org/xref/core/sw/source/uibase/shells/textsh1. > cxx#779 (/* Autocorrect from Basic */ is the comment at the ID). > > Any idea where this command comes from, Maxim? Looks unused to me. But anyway it should be safe to set the *Config flags in swriter.sdi to FALSE, and remove the string from WriterCommands.xcu.
(In reply to Maxim Monastirsky from comment #13) > ... should be safe to set the *Config flags in swriter.sdi to FALSE... Better solution would be to make starting autocorrection from toolbar possible.
Dear nemzag, 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
Dear nemzag, 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://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
Dear nemzag, 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