Created attachment 117962 [details] selection not possible below overflow arrow
Created attachment 117963 [details] selection not possible below overflow arrow
Created attachment 117965 [details] Sample file attached If we scroll, unable to make a selection on previously overflow hidden area.
please give a detailed step-by-step description how to reproduce the bug and tell your O/S
Well, the reporter’s OS is obviously Windows XP, as seen in the screenshots…
Step by step: 1 Open the attached file 2 Right-click on the arrow at the left of sheets tabs 3 You will see list of sheets names but not all (with my screen resolution, the last is 'sheet 63') 4 Scroll with mouse on this list 5 Click on sheet name after the last previous showned (exept the 1st one, in my case after 'sheet 64') Nothing happens.
Created attachment 117986 [details] sheet selection possible Please see blue colour selection - mouse over area on screen shot.
Created attachment 117987 [details] sheet selection not possible please see the sheet 57 with mouse over. but no blue colour & also no selection possible. earlier it was below the overflow scroll indicator.
confirming on Windows 8.1 Pro 64-bit en-US with Version: 5.0.2.2 (x64) Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe Locale: en-US (en_US) Better STR: 1. Create a new Calc document 2. Add a dozen of new sheets to the spreadsheet using the "+" button 3. Right mouse "context" menu selection of the "<" or ">" button will show the dozen sheets by name, and any of them can be selected. Calc focus moves to that sheet. 4. Add several more dozens of sheets. 5. Context menu will reach a vertical limit of the monitor size, and extends off screen (happens for me with 56 sheets exposed on 1920x1200 monitor). 6. The context menu can be scrolled downward into range of sheets not initially shown. 7. Mouse click selection of any of these "off screen" sheets from context menu has no effect, and sheet with focus remains where it had been. @Tomaž, one you might be interested in if you revisit bug 93318
*** This bug has been marked as a duplicate of bug 92702 ***