Trying to use Find and Replace in full screen causes serious problems, at least in Writer in OS X 10.11. If I open a document in full screen, it starts off working alright. If I scroll to the top, I see the buttons to leave fullscreen. I can also see that there is a keyboard shortcut to enter or leave fullscreen, but it is broken and deserves its own bug listing. If I open find & replace, while editing a document in full screen, find & replace goes into fullscreen, and blocks any view of the underlying document. I might be able to use split view, but haven't figured that out. If I close find & replace, while editing a document in full screen, it the full screen buttons do not return. At this point the only way out of fullscreen is to save one's work and quit.
Confirming on LO 5022 This is a particularly cumbersome bug linked to LO's still incomplete support of Apple's fullscreen mode
*** Bug 95738 has been marked as a duplicate of this bug. ***
Retested this bug. Version: 5.3.0.0.alpha0+ Build ID: cbf36dd473fdc9e8d8b78c9e9317836a7cbbc6c7 CPU Threads: 4; OS Version: Mac OS X 10.11.5; UI Render: default; TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2016-06-01_00:32:05 Locale: de-DE (de.UTF-8) When I am in fullscreen ✘ ⌘F expected: should open "find" bar currently: nothing ✘ alt⌘F expected: find & replace dialog curently: nothing @Jay: any thoughts, how this should be behaving. is this shortcut related?
@Steve: On linux, the shortcuts for the find bar or dialog dont work in fullscreen mode.
So i tested some more an the find toolbar will appear the first time you enter fullscreen mode, but not consecutive times. @maxim, @samuel: Any insight on why this isnt working consistently? @ux-advise: Should the find toolbar appear in fullscreen mode?
(In reply to Yousuf (Jay) Philips from comment #5) > @ux-advise: Should the find toolbar appear in fullscreen mode? Of course it has to. This ticket seems to be a bug on MacOS only as it works as expected under Windows. And Linux most likely as well.
(In reply to Heiko Tietze from comment #6) > Of course it has to. This ticket seems to be a bug on MacOS only as it works > as expected under Windows. And Linux most likely as well. Guess my comment 5 wasnt clear enough. This is not only a osx issue, it happens me on windows and linux.
*** Bug 91797 has been marked as a duplicate of this bug. ***
(In reply to Yousuf Philips (jay) from comment #7) > Guess my comment 5 wasnt clear enough. This is not only a osx issue, it > happens me on windows and linux. Yes, the issue is relevant on Linux as well. But it's not the toolbar (ctrl+F) that doesn't show up but the dialog (ctrl+H). And I still think it should be, other dialogs such as for styles show up as well in fullscreen mode.
(In reply to Heiko Tietze from comment #9) > (In reply to Yousuf Philips (jay) from comment #7) > > Guess my comment 5 wasnt clear enough. This is not only a osx issue, it > > happens me on windows and linux. > > Yes, the issue is relevant on Linux as well. But it's not the toolbar > (ctrl+F) that doesn't show up but the dialog (ctrl+H). And I still think it > should be, other dialogs such as for styles show up as well in fullscreen > mode. And to Windows. Would note that if the Find Bar is open and docked, or detached; or if the Find and Replace dialog is open--on shifting to Full Screen mode they both are not rendered. But then neither are other menus, toolbars or Sidebar decks (attached or floating). So believe it is simply a "feature" of full screen mode--only context menu actions can be activated, and only those dialogs present there. No short-cuts, e.g. F5 or F11 have effect. Maybe something specific to the mode should be added--to its context menus only--to launch specific dialogs, e.g. Find Bar, Find & Replace, Navigator, Styles & Formatting.
(In reply to Heiko Tietze from comment #9) > Yes, the issue is relevant on Linux as well. But it's not the toolbar > (ctrl+F) that doesn't show up but the dialog (ctrl+H). Yes the find & replace dialog doesnt work (bug 91797) but the toolbar also doesnt work in fullscreen with either of these steps. 1) Open Writer 2) View > Fullscreen 3) Press Ctrl+F top the toolbar and press Escape to close it 4) Press Escape to close fullscreen mode or press the fullscreen button 5) View > Fullscreen 6) Pressing Ctrl+F wont open the toolbar OR 1) Open Writer 2) Press Ctrl+F to open the toolbar 3) View > Fullscreen 4) Toolbar disappears and pressing ctrl+F wont make it reappear > And I still think it > should be, other dialogs such as for styles show up as well in fullscreen > mode. In my view, only dialogs should be accessible in full screen mode, as the mode intentionally disables toolbars, floating (non-modal) dialogs and the sidebar. To solve the issue of users pressing ctrl+f in fullscreen mode and it not working correctly, it should be coded into the Find toolbar command (vnd.sun.star.findbar:FocusToFindbar) to open the find & replace dialog if full screen mode is active. (In reply to V Stuart Foote from comment #10) > Maybe something specific to the mode should be added--to its context menus > only--to launch specific dialogs, e.g. Find Bar, Find & Replace, Navigator, > Styles & Formatting. I would believe this mode is intended to provide the maximum available space for users wanting to focus on their content and not have it taken up by various UI elements that are available in regular mode.
(In reply to Yousuf Philips (jay) from comment #11) > In my view, only dialogs should be accessible in full screen mode, as the > mode intentionally disables toolbars, floating (non-modal) dialogs and the > sidebar. Sounds like a guideline. To meet it, ctrl+H has to work properly and ctrl+F must never show the toolbar. On the other hand, why limit the options for users? It doesn't hurt anyone to show the quick find toolbar (as well as any other with shortcut) on demand.
(In reply to Heiko Tietze from comment #12) > Sounds like a guideline. To meet it, ctrl+H has to work properly and ctrl+F > must never show the toolbar. We should likely update the help to also state this. https://help.libreoffice.org/Common/Full_Screen > On the other hand, why limit the options for users? It doesn't hurt anyone > to show the quick find toolbar (as well as any other with shortcut) on > demand. As the find toolbar is the only toolbar that has a shortcut to activate it, and a find toolbar appears in full screen mode in your favourite browser, i think it should be kept and made to work correctly, especially as find & replace is a non-modal dialog. But i think we should limit how full screen should work, like we limit print preview mode from no editing. :D
(In reply to Yousuf Philips (jay) from comment #13) > We should likely update the help to also state this. > > https://help.libreoffice.org/Common/Full_Screen Adding the master of help to the CC list. Although, the question about toolbars in fullscreen mode feels to me still under debate.
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
*** Bug 120329 has been marked as a duplicate of this bug. ***
Dear MarjaE, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Can reproduce in: Version: 6.4.0.0.beta1 (x64) Build ID: 4d7e5b0c40ed843384704eca3ce21981d4e98920 CPU threads: 8; OS: Windows 10.0 Build 18363; UI render: GL; VCL: win; Locale: en-US (en_DK); UI-Language: en-US Calc: CL
Dear MarjaE, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug