Description: Ao selecionar a tabela inteira com o mouse e aplicar alguma modificação, como letras em negrito ou centralizar o texto, a modificação é aplicada em toda a tabela, exceto na primeira coluna da última linha selecionada. É um erro pequeno, mas que me faz perder tempo tendo que ir somente naquele quadrado aplicar as mesmas modificações novamente. Obs: Se eu fizer a seleção da tabela através das colunas, a modificação somente não é aplicada na primeira linha da última coluna selecionada. Steps to Reproduce: 1. Selecionar com a seta todas as linhas da tabela. 2. Aplicar qualquer modificação no texto. Actual Results: A primeira coluna da última linha não aplica as modificações. Expected Results: As modificações deveriam ser aplicadas à tabela inteira. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info:
On Win10 + LO 6.1.5.2, I don't reproduce this. Do you reproduce this on a brand new file or only on specific file? If specific file only, could you attach it to the bugtracker? (have in mind to remove any confidential/private part from it). Could you give a try to 6.1.5.2 (last stable LO version)? Remark: please try to use English so more people can involve.
Description: When you select the entire table with the mouse and apply some modification, such as bold letters or center text, the modification is applied throughout the table, except in the first column of the last selected row. It is a small error, but that makes me lose time having to go only in that square apply the same modifications again. Note: If I make the table selection through the columns, the modification is not applied to the first row of the last selected column. Steps to Reproduce: 1. Select all rows from the table with the arrow. 2. Apply any modification in the text. Current Results: The first column of the last line does not apply the modifications. Expected Results: Modifications should be applied to the entire table. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info:
(In reply to Julien Nabet from comment #1) > On Win10 + LO 6.1.5.2, I don't reproduce this. > > Do you reproduce this on a brand new file or only on specific file? If > specific file only, could you attach it to the bugtracker? (have in mind to > remove any confidential/private part from it). > Could you give a try to 6.1.5.2 (last stable LO version)? > > Remark: please try to use English so more people can involve. Yes, I did a lot of tests and the problem persists. I have already installed the 6.1.5 and the 6.2.1 versions of LibreOffice and have not solved the bug.
(In reply to Julien Nabet from comment #1) > On Win10 + LO 6.1.5.2, I don't reproduce this. > > Do you reproduce this on a brand new file or only on specific file? If > specific file only, could you attach it to the bugtracker? (have in mind to > remove any confidential/private part from it). > Could you give a try to 6.1.5.2 (last stable LO version)? > > Remark: please try to use English so more people can involve. I reproduced the test one more time in the version 6.2.1, this time with texts in the blocks, and I notice that the bug only happens when the block in the last line of the first column is blank. When have some text in this block, the modifications are applied normally.
I must miss something. Could you upload a file so I just use Menu Table/Select/Table then use "Bold"? Indeed, I could't succeed in reproducing this.
(In reply to Julien Nabet from comment #5) > I must miss something. > Could you upload a file so I just use Menu Table/Select/Table then use > "Bold"? > Indeed, I could't succeed in reproducing this. I made a video of this bug, but I couldn't uploaded as attachment, so I uploaded on Youtube: youtu.be/MU_dx5NIbSw
I can NOT reproduce on Version: 6.2.1.2 Build ID: 7bcb35dc3024a62dea0caee87020152d1ee96e71 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded I can NOT reproduce on Version: 6.3.0.0.alpha0+ Build ID: a03f421a878c210566dc8d728113a27400da38f2 CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-03-16_09:07:41 Locale: ro-RO (ro_RO.UTF-8); UI-Language: en-US Calc: threaded
don't repro in Version: 6.4.0.0.alpha0+ (x86) Build ID: d35171456bc230efdaa9426da1398b2db7fa0df8 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-06-27_04:11:18 Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
Dear Wagner Matos, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Wagner Matos, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp