https://bugs.documentfoundation.org/show_bug.cgi?id=171795
--- Comment #8 from Colin <[email protected]> --- (In reply to ady from comment #7) > This seems to be a visual problem, and therefore, in order to replicate the > issue with attachment 206730 [details], specific visual conditions must be > met; > > 3. Reduce the zoom factor to 120%. If the last row of the table is not > already (fully) displayed on screen (without having to scroll down), that > means that the zoom factor needs to be reduced even more (in order to be > able to replicate the visual problem). Both the first and the last rows of > the table must be simultaneously displayed on screen (without having to > scroll). > The characteristics of my monitor make it convenient to set the display to 200% giving me as much data as possible in the full screen AND I still often have to scroll down the screen to visualise all the data. I didn't initially realise that the magnification and "available" rows was forcing the displayed information up against the lower "ribbon". I now perceive this "overcrowding" as possibly being responsible for the "half-height" display, particularly as when the display magnification is reduced to ensure all the rows are visible on screen, then it is the top row "nudging up against" the "concealment area of the filtered out rows and that row then presents the slight truncation. Another observation: I mentioned the links to Excel sheets to satisfy more complex functionality. I am now observing some "illogical/inconsistent" refresh characteristics in Excel where certain actions appear to trigger a refresh "some of the time" but then that refresh will be delayed until perhaps two more actions have occurred and ultimately trigger the correct refresh. These are mostly related to conditional formatting used to highlight such events as which cell next requires action or simple colour scale heat maps. Could it be a windows related issue? Am I talking rubbish? I applaud @ady on the depth of his analysis -- You are receiving this mail because: You are the assignee for the bug.
