When I enter text in a cell starting with a "+" or a "-" (but NOT a valid formula, so it's text) which contains parenthesis "(" and ")", one of three things may happen, and I can't see a pattern: A- nothing special: the text is left as is, as it should be B- while typing, parenthesis that match become bold; but when you are finished editing, the bold disappears. This could be OK if you were entering a formula. C- same as B, but they do remain bold forever after you are finished editing This seems to have to do with the fact that when the input starts with + or - it is attempted to be interpreted as a formula. So, B might be expected behavior if the decision whether the input is a valid formula is taken only at the end. However, if the entered text is not a valid formula and turns out to be text (the proof being, that when you re-edit it, there's no added "=" sign at the beginning in the input field on the top of the screen), there's no reason for behavior C.
After some more tests, there might actually be a pattern: B seems to happen when the text starts with a "+", while C seems to happen when it starts with a "-". Equally nonsense.
I always have the case B. I think it is the highlighting of matching parenthesis. So not a bug. Tested with LO 5.1.1.0.0+ under Ubuntu 15.10 x86-64. Could you try with LO 5.1.0 RC2 ? Best regards. JBF
I can't test the version you ask me, but I've just upgraded Ubuntu to 15.10 and tested 5.0.2.2 and the issue persists. I was wrong about this: > B seems to happen when the text starts with a "+", > while C seems to happen when it starts with a "-" I get C also in cases where the text starts with a "+". It's totally random, I have just observed the issue disappear on a cell after editing the contents, and then edited again to the exact original value and the issue did not reappear. For example, say the contents of the cell were: -(foobar) the parenthesis remained bold. Then I changed the content to: -(foo) the bold disappeared after editing. I restored the original value: -(foobar) the bold did not reappear.
Created attachment 122120 [details] printscreen I can confirm with Version: 5.2.0.0.alpha0+ Build ID: d95d9d7f908419f397941ef60ac6ced3261c9b87 CPU Threads: 4; OS Version: Linux 4.2; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2016-01-19_00:40:21 LibreOffice 3.5.0 Build ID: d6cde02 C- same as B, but they do remain bold forever after you are finished editing
** 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
Dear teo8976, 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 teo8976, 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
Issue still exists in version: Version: 7.2.3.1 / LibreOffice Community Build ID: 20(Build:1) CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: an-ES (an_ES.UTF-8); UI: en-US Calc: threaded
*** Bug 152271 has been marked as a duplicate of this bug. ***
Still repro: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL Steps (case A): 1. New Calc 2. A1: -(foobar) [ENTER] > parentheses are bold; this boldness is displayed immediately after the second parentheses is typed-in, not before. 3. A1: Click on the formula bar at the right-side of the closing parentheses (do _not_ use F2). 4 You might notice that the "B" icon is not indicating that the parentheses is bold. Move around the characters, back and forth if you need to. Press [ESC] without editing anything. 5. Click again on the formula bar at the right-side of the closing parentheses (do _not_ use F2). After a split second, note that the "B" icon shows that the ")" is bold. Move the cursor around and it is clear that both parentheses are bold whereas the rest of the text is not. Don't press [ENTER] yet. 6. Edit the text from "foobar" to "foo". Don't press [ENTER] yet. 7. Move the cursor to the end of the inputwin, to the right-side of the closing parentheses. Note the "B" icon is still "on". Now press [ENTER]. Note that the bold attribute remains for both parentheses. 8. You can now edit the cell, whether by clicking on the formula bar or by F2; the parentheses are left as bold. The only remedy is to either select each and make them regular (i.e. _select_ one parentheses, click on the "B" icon twice or press [CTRL]+[B] twice, repeat for the other parentheses), or alternatively delete both parentheses, press [ENTER] and add them again. Please note that in step 3 above, I do not use F2. Now you can repeat the whole procedure, except that in step 3 use F2 to enter into edit mode, instead of using the mouse – lets call this case B. Use then only the arrows in your keyboard to edit the text from "foobar" to "foo" and press [ENTER]. In case B, the parentheses are no longer bold. They were bold initially, as if you were typing a possible formula. This is OK, until the first [ENTER], when the cell is no longer considered a potential formula but an established text. Unless the user sets the bold attribute to a character, it should not remain bold after pressing [ENTER]. In case A, the parentheses, as text/characters, have the bold attribute fixed, so it is as if you have manually already set this attribute to that characters. But this attribute seems to be assigned to the parentheses at the moment when clicking on the formula bar, which is the difference between case A and case B, because before that moment, case B shows that the bold attribute was not still assigned (or, alternatively, it gets unassigned). There are 2 more tests, and that is with: Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0484a9a3f5e2ecb678f6fb41bbb251529e89c00d CPU threads: 4; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win Locale: en-US (es_AR); UI: en-US Calc: CL threaded Built 2023.03.07 ...in which the apostrophe plays a role. With the mouse (as in case A above), all is the same. With F2, an apostrophe is eventually shown in the formula bar. You have to edit the cell and press [ENTER] in order for the apostrophe to be displayed in the inputwin. Although I have not tested with LO 7.5, I guess this will happen in that version too, because the modified behavior was introduced for that version.