Bug 138746 - Two undo steps when using 'clear direct formatting' from set paragraph style dropdown in the toolbar
Summary: Two undo steps when using 'clear direct formatting' from set paragraph style ...
Status: RESOLVED DUPLICATE of bug 132890
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-12-08 16:51 UTC by Telesto
Modified: 2021-06-23 06:26 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-12-08 16:51:18 UTC
Description:
Two undo steps when using 'clear direct formatting' from set paragraph style dropdown in the toolbar

Steps to Reproduce:
1. open attachment 167979 [details]
2. Select the second row (2 educated)
3. Select clear direct formatting select style drop down
4. Press Undo (nothing
5. Press undo again (proper)
6. Compare with -> Format -> Clear Formatting

Actual Results:
Using style picker, clear formatting generates 2 undo steps

Expected Results:
1 undo steps, similar to Format -> Clear direct formatting


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.2.0.0.alpha0+ (x64)
Build ID: 796c7f612603490dda9277ced0f6ab3cce3bc116
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-12-08 16:52:38 UTC
Also in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL
Comment 2 Telesto 2020-12-08 16:53:42 UTC
And in
LibreOffice 3.5.0rc3 
Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735
Comment 3 Dieter 2021-06-23 06:26:52 UTC
This is again a duplicate of your own bugs. It would save a lot of time, if you would search for duplicates before reporting. I loose motivation to work on your reports.

*** This bug has been marked as a duplicate of bug 132890 ***