Bug 150373 - Updating styles (Ctrl+Shift+f11) removes the new created style
Summary: Updating styles (Ctrl+Shift+f11) removes the new created style
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.4.0.0 beta1+
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL: https://help.libreoffice.org/7.5/en-U...
Whiteboard:
Keywords:
Depends on:
Blocks: Styles-Management
  Show dependency treegraph
 
Reported: 2022-08-11 17:26 UTC by grishka@zaclys.net
Modified: 2022-08-14 09:12 UTC (History)
0 users

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description grishka@zaclys.net 2022-08-11 17:26:46 UTC
Description:
Paragraph styles are not updated after a style modification directly in the text. On the contrary, the initial style is reactivated when the update option is activated (by clicking in the panel or in the "Style" menu, or with Ctrl+Shift+f11).

(The modification with the style editing menu works, only the update option has a problem)

Steps to Reproduce:
1. Apply a style to a paragraph (Heading 1, for example)
2. Change the appearance of the title (Font size, Bold)
3. Activate the style update

Actual Results:
the initial style is reactivated

Expected Results:
The new style should apply to all paragraphs of the same style (to all Headings 1 in the example)


Reproducible: Always


User Profile Reset: No



Additional Info:
I use Libreoffice for Debian.
Comment 1 Timur 2022-08-12 14:37:40 UTC
I see this working, so NotABug, if in step 2. you change the appearance of the whole paragraph, as explained in Help.
Doesn't work for a part.

If I didn't understand, please set Unconfirmed.
Comment 2 Timur 2022-08-12 15:05:41 UTC
Other possibility is to change this to enhancement, to enable updating styles from a selected part of a paragraph.
Comment 3 Timur 2022-08-14 09:12:14 UTC
See also bug 76084.