In order to reproduce the bug: [1] Open new text document and insert a simple table. [2] Display table styles in sidebar. [3] Right click a predefined table style. A context menu only with the item “Hide” is displayed. Here the style can't be deleted. [4] Click into table. [5] Open dialogue AutoFormat: Table > AutoFormat Styles… [6] Select a predefined table style e.g. Box List Blue. [7] Click Delete. Then OK. The deleted style is no longer listed in AutoFormat dialogue. Expected: Delete button should be greyed and a deletion of a predefined style should not be possible. [8] Close dialogue with Close. In the sidebar the deleted style is still displayed. Expected: No display of deleted style. (Now you can even assign the deleted style to a table. Strange!) [9] Close the document without saving. [10] Open another new text document and display the table styles in the sidebar. Now the deleted style is no longer listed. There is no simple way to get the deleted table style back. I only know the possibility to delete the user profile with all its disadvantages. The bug exists similarly in all versions. Hence inherited from OOo.
confirm in Version: 6.4.0.0.alpha0+ (x86) Build ID: ca6df519a78e5bfc96030c916f242b86306194e5 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: threaded
The current implementation does not allow to remove hard coded TS. So what we have to do, is to disable the Delete button in this case. OTOH, the Autoformat dialog will be removed once the new TS edit dialog is implemented. So close as WF or hope for dev effort?
When you create a new TS per sidebar it's shown there but not in the autoformat dialog (the TS is stored in the document only and disappears when closed). Doing this per dialog makes the style permanent.
Code pointer: https://opengrok.libreoffice.org/xref/core/sw/source/ui/table/tautofmt.cxx?r=d5d99478#289 (sc has extra code and should be handled in the same way!).
Dear Harald Koester, 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 Harald Koester, 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