Bug 111753 - Misbehavior of default formatting option used on Impress table
Summary: Misbehavior of default formatting option used on Impress table
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: ImpressDraw-Tables
  Show dependency tree / graph
 
Reported: 2017-08-13 01:20 UTC by Tamás Zolnai
Modified: 2023-04-16 03:24 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tamás Zolnai 2017-08-13 01:20:50 UTC 
Description:
After setting a character property (e.g. strikthrough) and use default formatting option the character attributes are set back to default. However if I change the text's vertical alignment the strikthrough comes back.

Steps to Reproduce:
1. Open Impress
2. Create a table
3. Add some text to the cell and select the text
4. Set strikthrough using sidebar
5. Select the whole table as object
6. Click Default Formatting in context menu (-> strikthrough is removed)
7. Change vertical text alignment using sidebar (-> strikthrough is back)

Actual Results:  
Strikethrough somehow comes back when changing the vertical text alignment.

Expected Results:
Strikethrough should not reapplied on the text.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36
Comment 1 Regina Henschel 2017-08-13 17:24:45 UTC 
Reproducible with the given steps in Version: 6.0.0.0.alpha0+
Build ID: 1176ae51154c2298b44427270754d2ee1562a115
CPU threads: 4; OS: Windows 6.1; UI render: default; 
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-07-27_12:54:56
Locale: de-DE (de_DE); Calc: group

I think, that here are three bugs:
(1) After applying the strike-through the expected behavior is, that there is a <text:span> element, that refers a text style with strike-through set. But not only this text style is created, but there is a paragraph style and a cell style created, both with strike-through set.
(2) After applying "Default Formatting", the text and paragraph styles are removed. But the cell style is kept. Therefore the text should be still shown in strike-through.
(3) After applying "Default Formatting" the cell-style is not removed.

Besides that, there is the general problem, that there are no styles available for the user, neither for text, nor paragraphs, nor table cells and therefor it is not possible for the user to know, what is really set, if he uses "Default formatting".
Comment 2 QA Administrators 2018-08-14 02:32:51 UTC Comment hidden (obsolete)
Comment 3 Regina Henschel 2018-08-14 09:42:29 UTC 
Step 6 is no longer possible. In case the table or a column is selected, the context menu has no item "Default formatting" and the item "Clear Direct Formatting" in menu Format is disabled. In case a row is selected, the items are active but they do nothing. Only in text edit mode the items work and can be used as expected. In text edit mode you see "Text Edit" in the status bar.

It is partly solved. In case a row is selected, the items should be disabled too, because they do nothing.

But the basic problem is still not solved, that it is not possible to remove all direct formatting on all selected cells of a row, column or table.

Tested with Version: 6.2.0.0.alpha0+ (x64)
Build ID: d54861bac28c0c6dd84bca6a9c1ddeb76de184a8
CPU threads: 8; OS: Windows 10.0; UI render: GL; 
Locale: de-DE (en_US); Calc: threaded
Comment 4 QA Administrators 2021-04-15 03:43:15 UTC Comment hidden (obsolete)
Comment 5 QA Administrators 2023-04-16 03:24:39 UTC 
Dear Tamás Zolnai,

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