OS: Windows 10 Windows not switching when Writer is running as the topmost window : When clicking other icons on the task bar, the usual scenario is switching to that particular task, with its window coming to the topmost, thus the user can work with the APP right away. Writer sometimes (not always) behaves monopolizing the PC screen, not getting off by remaining as the topmost. The only thing that can be done is clicking the "minimize" icon on its own window, thus making it shrink into the task bar, thereby releasing control to the other APP. CSLam
Can not confirm. On Windows 10 Home 64-bit en-US Intel i5-7500 with HD 620 GPU and 16GB Ram Version: 5.4.0.3 (x64) Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb CPU threads: 4; OS: Windows 6.19; UI render: default; Locale: en-US (en_US); Calc: group Multiple LO documents open along with multiple other apps--Windows 10 taskbar switching is clean with selected document gaining focus. Windows <Alt>+<Tab> bar switching is also crisp between LO documents.
As said, the irregularity does not always happen. Another interesting scenario that I have experienced multiple times perhaps adds to the thought. Within the Writer document, I choose to create a spreadsheet from the menu bar (as I want to copy a table, turning it into a spreadsheet for some other purposes); The correct response: A new Calc spreadsheet comes up allowing me to proceed further. Occasionally, the response is something like this: A new Calc spreadsheet is created, but the Writer screen remains, as if nothing has been done. However, there is a Calc icon generated in the Windows task bar. I cannot go into the spreadsheet by clicking it, only by minimizing the Writer window. The problem only comes from time to time. I have not tried Alt-Tab (because I already know how to fix it, though in a rather ugly manner), and will try this when I go into the situation again. CSLam
Thank you for reporting the bug. Unfortunately without clear steps to reproduce it, we cannot track down the origin of the problem. Please provide a clearer set of step-by-step instructions on how to reproduce the problem. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the steps are provided
As said, it does not always happen. Please see my second post, which triggers the issue from time to time - but not always. CSLam
(In reply to CSLam from comment #4) > As said, it does not always happen. Please see my second post, which > triggers the issue from time to time - but not always. > > CSLam Did you find any way to reproduce it systematically?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20180530
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20180703