Bug 126275 - Can't find & replace by paragraph styles at once after find by font attributes
Summary: Can't find & replace by paragraph styles at once after find by font attributes
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
4.2.8.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Find&Replace-Dialog
  Show dependency treegraph
 
Reported: 2019-07-07 20:02 UTC by Roman Kuznetsov
Modified: 2025-06-03 03:10 UTC (History)
2 users (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 Roman Kuznetsov 2019-07-07 20:02:45 UTC
Description:
Can't find & replace by paragraph styles at once after find by font attributes

Steps to Reproduce:
1. Open Writer
2. Ctrl+H (Edit->Find & Replace) to open F&R dialog
3. Push Attributes button
4. Select Font weight in list and push OK (do not close F&R dialog!)
5. Push Attributes button again
6. Unselect Font weight in list and push OK (do not close F&R dialog!)
7. Check Paragraph styles checkbox
8. Try select style in find or replace drop-down list
9. It are empty
10. Close F&R dialog
11. Open F&R dialog
12. Check Paragraph styles checkbox
13. Try select style in find or replace drop-down list
14. It works as expected

Actual Results:
Can't find & replace by paragraph styles at once after find by font attributes

Expected Results:
Can find & replace by paragraph styles at once after find by font attributes


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 6.4.0.0.alpha0+ (x64)
Build ID: a9885aed4ee65067613e5506771b6ae6b5e0bae0
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-07-04_01:38:09
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded

and I checked it in to 4.2.8.2 build 

possible inherrited from OOo
Comment 1 Dieter 2019-07-08 15:12:43 UTC
I confirm it with

Version: 6.4.0.0.alpha0+ (x64)
Build ID: ae823e4633a76d13cebc6432b9e44b9b2862326b
CPU threads: 4; OS: Windows 10.0; UI render: GL; VCL: win; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2019-06-26_23:06:07
Locale: de-DE (de_DE); UI-Language: en-US
Calc: threaded
Comment 2 Dieter 2021-06-02 07:17:37 UTC
Still present in

Version: 7.2.0.0.alpha1+ (x64) / LibreOffice Community
Build ID: 4a9eef7849a75ba91806886ea9c96d114c8d56f9
CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 3 QA Administrators 2023-06-03 03:16:25 UTC Comment hidden (obsolete)
Comment 4 Roman Kuznetsov 2023-06-03 15:35:09 UTC
Still repro

Version: 7.6.0.0.alpha1+ (X86_64) / LibreOffice Community
Build ID: 2b3b4026a5c6a1b92c0b29b94dd62a4c3c7b9fad
CPU threads: 16; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: CL threaded
Comment 5 QA Administrators 2025-06-03 03:10:49 UTC
Dear Roman Kuznetsov,

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