Created attachment 105814 [details] see page 4 and 5 1) creating a new table on a page with button Table (toobar button) --> a table is created with one line grey, one line dark grey, etc. 2) Write some words in each box of the first column 3) Write some words in other column and select these boxes --> many boxes are selected but not all the table 4) try to change colors or size text through fill button toobars --> Size apply to all texts even out of the selection --> selecting Grey 1 (first grey under black fill color) fill selected boxes in black. Try again grey 1, it's OK
Tested with same problem on version 4.3.1.2. By the way, 4.3.0.4 don't see any update : I've to download 4.3.1.2 myself.
reproducible with LO 4.3.1.2 (Win 8.1) Remarks to step 4: Change the font size with the icons INCREASE FONT and REDUCE FONT and change the font color with the icon FONT COLOR in the toolbar at the top. Result: Increasing and decreasing the font size changes the size of the whole text and not only of the selected cells. Pressing the icons INCREASE or REDUCE FONT leads to loosing the selection, but the selection should be kepted -> Faulty. Therefore, for changing the FONT COLOR in the next step the selection needs to be redone. But then only the selected cells are changed -> Correctly.
Bug 46917 added to See Also list.
*** Bug 89839 has been marked as a duplicate of this bug. ***
** 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.5 or 5.1.2 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: 2016-04-16
This bug is still present in LibreOffice 5.2.2. Build ID: 1:5.1.2~rc2-0ubuntu1~wily0 Andy's remarks in comment #2 still pertains.
I tested with LibreOffice 3.3.0 OOO330m19 (Build:6) tag libreoffice-3.3.0.4 on Kubuntu 15.10. It is the same. Version changed to inherited from OOo.
Can someone else try these operations with LO5.3.1 or superior ? It seems to be partially fixed (but not commented)... Size text bug still there.
Tested under 5.4 : the bug isn't the same now. Selecting a row (or a line) and changing formatting font size is ok (with REDUCE button or INCREASE button) : now Bug is you can't do it twice time because after the first click, the selection disapear and all the table become selected.
** 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
Problem solved in LO6.2.0.3 Thanks!
(In reply to roumanet from comment #11) > Problem solved in LO6.2.0.3 > Thanks! Thanks for retesting with the latest version. Setting to RESOLVED WORKSFORME as the commit fixing this issue hasn't been identified.