Summary: | main menu pop-up isn't on its normal place | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Roman Kuznetsov <79045_79045> |
Component: | UI | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | 79045_79045, miguelangelrv, m.weghorn, telesto |
Priority: | medium | Keywords: | bibisectRequest, regression |
Version: | 24.2.0.0 alpha0+ | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 85811 |
Description
Roman Kuznetsov
2023-07-26 20:05:22 UTC
I've seen a similar issue on Linux with kf5 and gtk3, but no more with current master. I didn't check further, but I suspect that it may have been caused by commit ea3317188589554ea5773db53aa9e0cc88bee271 Author: Noel Grandin Date: Tue Jul 25 20:59:19 2023 +0200 simplify logic in FloatingWindow::ImplCalcPos no need to convert this position backwards and forwards Change-Id: Iba4ebcba420025865638c99fa143ea0d7d262805 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154901 Tested-by: Jenkins Reviewed-by: Noel Grandin and fixed by the corresponding revert: commit 2b3dcd24e4da1f83bfaf8e0ffd93839eeae621b0 Author: Noel Grandin Date: Wed Jul 26 10:35:36 2023 +0200 Revert "simplify logic in FloatingWindow::ImplCalcPos" This reverts commit ea3317188589554ea5773db53aa9e0cc88bee271. Reason for revert: There are 3 different coordinate systems at work here, not 2, my mistake. Change-Id: Iee69b8ba3c2fe60b26b118e79116035be42c6c45 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/154922 Tested-by: Jenkins Reviewed-by: Noel Grandin Do you still see this with a current daily build/git master? Looks like a dup of tdf#156479, set up now a RESOLVED FIXED. yeah I don't see the problem in Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: cf8f7b91f41821b79495c0388359c4cb1156ea67 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 *** This bug has been marked as a duplicate of bug 156479 *** |