STEPS TO REPRODUCE: format a table with a header row, format the header using a cusotom header row paragraph style. apply the newly created autoformat to a new table. RESULT: the header row will look like the original header. But the paragraph styles of the original table are not applied. EXPECTED RESULT: that the paragraph styles are applied. PERSONAL SIDE NOTE: This is my first document with a LOT of tables in LO. It will most probably be the last - formatting a lot of tables is a serious pain in ... ... .
Please attach a document that makes it easier for us to repro. Setting to NEEDINFO - once you attach a simple document, please set to UNCONFIRMED. Thanks!
Created attachment 116719 [details] The result of the failed application of a paragraph style with autoformat If you know what to look for (paragraph styles in the table header row) you can see what is NOT there - which is the paragraph style "Table Heading" in the header row.
If you redefine your default Table Header paragraph style in the styles and formatting dialog rather than via AutoFormat > New, this appears to work OK. By default, if the Table Header option is not clicked in the Table Properties dialog, the first row will be assigned the Table Content paragraph style. When you tick the Table Header option in the Table Properties dialog, the default Table Header style is applied (even if you have set a different paragraph style. In order to change this, you need to change the default Table Header style in Styles and Formatting - I would admit that this kind of defeats having an AutoFormat > New dialog, if you can't set up your own customised paragraph styles as well. Confirming
Setting as: Minor - slows down professional quality work but will not prevent it; Low - default for minor issues. Would be nice to find out if this is a regression or not (testing 3.3 and seeing if the issue was around there would tell us that information). http://downloadarchive.documentfoundation.org/libreoffice/old/
Well, MS Paint also makes professional work hard but possible :) . After editing only a single document I must say tables in LO need a _much_ better approach. But to the point: Checked version 3.3.4.1, same thing.
** 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.1.5 or 5.2.1 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-20160920
unchanged, still open LibreOffice 5.1.5.2 Build ID 7a864d8825610a8c07cfc3bc01dd4fce6a9447e5 Mac OS X 10.12 Locale: de-DE (de_DE.UTF-8)
** 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
Bug still present. LIBREOFFICE INFORMATION: Version: 5.4.2.2 Build ID: 22b09f6418e8c2d508a9eaf86b2399209b0990f4 CPU threads: 8; OS: Mac OS X 10.13; UI render: default; Locale: de-DE (de_DE.UTF-8); Calc: group STEPS TO REPRODUCE: * add table * format table header with PARAGRAPH STYLE "Table heading" * format table contents with PARAGRAPH STYLE "Table contents" * create a table auto-format from that * Table auto-format dialog * Use "Add" when table is marked to add new format type * Create NEW table * format table with table auto-format style. RESULT: * The PARAGRAPH STYLES are *NOT* applied * ... just the formatting is. EXPECTED RESULT: * the formatting is not applied, * but the PARAGRAPH STYLE is. That is a real PITA if you format a lot of tables and want to change all headings / contents at once.
set version field to "inherited from ooo" cause I already tested with 3.3.4.1, as per the instructions.
This is still present. Note: Important to check the paragraph style! The formatting (e.g., bold header) is applied, but the paragraph style is not. As such, you lose the format if you press ctrl+m (presumably resetting format) Version: 6.3.0.0.alpha0+ Build ID: beae6c7a7f163daad0d4dea63a3d403af2745fd1 CPU threads: 2; OS: Mac OS X 10.13.6; UI render: default; VCL: osx; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-12-06_23:52:29 Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
This is now fixed Version: 7.0.0.0.alpha0+ Build ID: f14691683900f6b28737be8c599e1ee4e8386e14 CPU threads: 4; OS: Mac OS X 10.14.6; UI render: default; VCL: osx; Locale: en-US (en_US.UTF-8); UI-Language: en-US Calc: threaded
No change - repro 7.1+ using Linux. The paragraph style on the first row is still "Table Contents" and not "Table Header". Ctrl-M still removes the copied formatting.
No change - repro 7.1+ using Linux. The paragraph style on the first row is still "Table Contents" and not "Table Header".
*** This bug has been marked as a duplicate of bug 104389 ***