Bug 141257 - "Styles" panel is not isolated between Writer running windows processes
Summary: "Styles" panel is not isolated between Writer running windows processes
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.1.1.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-26 00:05 UTC by rafael.linux.user
Modified: 2022-04-11 09:31 UTC (History)
3 users (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 rafael.linux.user 2021-03-26 00:05:46 UTC 
When you have two or more Writer processes running, if you have two Writer windows showing two documents with different Paragraph Styles and you have enabled "Styles" tool bar (F11), you will see the current Styles of the active Writer window in the Styles preview panel. Every time you switch from one Writer window to the other, bot Styles preview changes simultaneously, showing in both the selected Writer window styles.
Comment 1 rafael.linux.user 2021-03-26 20:52:29 UTC 
You must have the two Writer processes (with two distinct documents with distinct styles) showed side by side in your screen, showing in both Writer windows the "Paragraph styles" side panel.
Comment 2 Dieter 2021-04-12 12:13:53 UTC 
I can't confirm it with

Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 807d059d99e7b99fe45a712428befa17ffa44858
CPU threads: 4; OS: Windows 10.0 Build 19042; UI render: Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: en-GB
Calc: CL
Comment 3 Buovjaga 2022-04-01 08:20:59 UTC 
How are you running them? Separate versions with separate user profiles? Sharing a user profile? Could you attach a video capture of how it behaves?
Comment 4 rafael.linux.user 2022-04-11 09:27:38 UTC 
It seems it's fixed (at least in Linux version) so I'll close this bug if I can do it.
Comment 5 Dieter 2022-04-11 09:31:36 UTC 
(In reply to rafael.linux.user from comment #4)
> It seems it's fixed (at least in Linux version) so I'll close this bug if I
> can do it.

Thank you for retesting. Please use status RESOLVED WORKSFORME in such a case.