Bug 155732 - Entries not related to any style in the drop down should use the UI default
Summary: Entries not related to any style in the drop down should use the UI default
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
7.6.0.0 alpha1+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Writer-Styles
  Show dependency treegraph
 
Reported: 2023-06-08 10:04 UTC by Telesto
Modified: 2025-06-09 03:10 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 2023-06-08 10:04:33 UTC
Description:
The font (type & size) of some entry's in the Set Paragraph Style drop down are following the applied font. 

Steps to Reproduce:
1. Open Writer
2. Type ABC
3. Select ABC
4. Go to Set Paragraph Style drop down in the toolbar and expand it (arrow down)
7. Look at font for 'Clear Formatting' & 'More Styles'
8. Apply Heading 1
9. Expand the Set Paragraph Drop down again. Look at 'Clear Formatting' & 'More Styles'  

Actual Results:
The font is adapted to the current font

Expected Results:
Independent font/ font size


Reproducible: Always


User Profile Reset: No

Additional Info:
Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 389a8d52d9961f89c0b2847b30ee1ca59a8fdc80
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 threaded
Comment 1 Heiko Tietze 2023-06-09 07:57:23 UTC
The dropdown shows the font in a (limited) WYSIWYG way in, for example, red if the style has set this attribute. It's done deliberately.

Maybe you have the items in mind that are not related to any style, ie. Clear Formatting and More Styles, you are right. At least the "More Styles" item takes attributes from the preceding "Heading" and become italic if I change the style.
Comment 2 QA Administrators 2025-06-09 03:10:46 UTC
Dear Telesto,

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