Bug 136340 - Reset doesn't reset in paragraph style dialog after pressing apply
Summary: Reset doesn't reset in paragraph style dialog after pressing apply
Status: RESOLVED DUPLICATE of bug 128469
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.1.0.0.alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsUXEval
Depends on:
Blocks:
 
Reported: 2020-08-31 19:29 UTC by Telesto
Modified: 2020-09-16 04:08 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 Telesto 2020-08-31 19:29:41 UTC 
Description:
Reset doesn't reset in paragraph style dialog after pressing apply

Steps to Reproduce:
1. Open the attached file
2. Sidebar -> Styles -> Right click -> Default Paragraph Style -> Modify
3. Font effects tab
4. Choose a font color & press apply
5. Press Reset

Actual Results:
Nothing happens

Expected Results:
I assumed that Apply can be used how it looks on screen; with the possibility to 'reset' the original (until dialog gets closed). The reset button functions to reset to last applied state. With some bad luck you press 'Standard' which is of course again something different


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.1.0.0.alpha0+ (x64)
Build ID: 1e0cfd5662d95cea84e80e4fe10d52c3b1101ae6
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win
Locale: nl-NL (nl_NL); UI: en-US
Calc: CL
Comment 1 Telesto 2020-08-31 19:32:34 UTC 
They 'reset' is slightly ambiguous. At least I have another expectation compared to what it actually does. 

And what I expect is what the help says

"Resets changes made to the current tab to those applicable when this dialog was opened."
Comment 2 Heiko Tietze 2020-09-15 10:38:38 UTC 
Yes, this is in discussion. You are welcome to join the duplicate.

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