https://bugs.documentfoundation.org/show_bug.cgi?id=153515
--- Comment #6 from Alexander Berg <[email protected]> --- (In reply to V Stuart Foote from comment #5) > (In reply to V Stuart Foote from comment #4) > > Testing Version: 25.2.1.2 (X86_64) / LibreOffice Community > > Build ID: d3abf4aee5fd705e4a92bba33a32f40bc4e56f49 > > CPU threads: 8; OS: Windows 10 X86_64 (10.0 build 19045); UI render: > > Skia/Vulkan; VCL: win > > Locale: en-US (en_US); UI: en-US > > Calc: CL threaded > > > > Direct closing <Ctrl>+Q from a full screen <Ctrl>+<Shift>+J module (Writer > > or Calc) still records the ooSetupFactoryWindowAttributes with other than > > "1", or "4" > > > > At this point it receives a "65", and on restart of the module it does not > > open to full screen--but it does position the document canvas within the app > > frame as if it were from full screen. > > > > I no longer have multi-monitors to work against. > > > > But there continues to be some issue with the configuration/placement of a > > module closed from full screen mode. Of course only Writer or Calc are > > affected. > > It no longer is jumping to the 0,0 position and the app frame is positioning > to and taking the x,y size as recorded to the > ooSetupFactoryWindowsAttributes stanza--just the positioning of the document > within the app frame is off. I don't understand what this means. However, there was a time when it worked perfectly. QA Administrators wrote to me and asked if the bug still existed, to which I replied to his question. -- You are receiving this mail because: You are the assignee for the bug.
