Description: "it's weird that once you click Ok, LO goes back automatically to paragraph styles instead of staying on frames styles" Steps to Reproduce: 1. Open Writer 2. Sidebar -> Styles 3. Frame tab 4. Right click Graphic -> Modify 5. Press Cancel 6. Tab switches to Paragraph -> Tab switch 7. Go to frame again 8. Right click Graphic -> Modify 5. Press Cancel -> No tab switch -> Graphic still selected 1. Open Writer 2. Sidebar -> Styles 3. Frame tab 4. Right click Graphic -> Modify 5. Press OK 6. Tab switches to Paragraph -> Tab switch 7. Go to frame again 8. Right click Graphic -> Modify 5. Press OK -> No tab switch & nothing selected in the sidebar Actual Results: Behavior different between first & second time pressing OK/Cancel Behavior is different between pressing OK or Cancel the second time Expected Results: Should be coherent.. And I agree with Julien: it's weird that once you click Ok, LO goes back automatically to paragraph styles instead of staying on frames styles" but probably a bigger picture.. Reproducible: Always User Profile Reset: No Additional Info: Version: 7.1.0.0.alpha0+ (x64) Build ID: 41d8b41767032681a9897b7551f011d450e3725e 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
And the pressing OK behavior is also wrong; It moves focus to the top. See bug 133206
After editing styles in the sidebar the focus goes back to the document and you get the currently active style selected, which is usually PS. Is this a duplicate of 133385, kind of?
(In reply to Heiko Tietze from comment #2) > After editing styles in the sidebar the focus goes back to the document and > you get the currently active style selected, which is usually PS. Is this a > duplicate of 133385, kind of? bug 133385 is fixed in master. @Telesto, is this issue still reproducible in master ?
Still repro.. only with an empty doc
In principle the same root cause as described in bug 133206.
(In reply to Thomas Lendo from comment #5) > In principle the same root cause as described in bug 133206. *** This bug has been marked as a duplicate of bug 133206 ***