2016 06 23 Display scrolls when opening filter in a pivot table. Problem description: In a sheet with a pivot table, if the currently selected cell is out of the visual display, when opening one of the filters with one click, the filter panel opens and closes, then scrolls down or right to display the selected cell. Steps to reproduce: Open test file provided. Go to the sheet of the pivot table, select cell A46 with a mouse click. Go back to the top with the scrolling bars or the scrolling wheel of the mouse. Open Field4 filter panel with one click. The filter panel opens and closes. The display scrolls down to display the selected cell. Repeat test but select cell U8 on the right side. The filter panel does the same. The display scrolls right to display selected cell. If we click on the filter and keep the left button of the mouse pressed, the panel stays open but could not select anything; releasing the mouse click causes the filter panel to close and the display scrolls to display the selected cell, down or right. If the selected cell is inside the display area of the screen it will perform ok. If the selected cell is the last partial visible cell, the problem reproduces. This behavior is related to the Auto Filter as well, for that, I will file another bug report. Tested with LO Version: 5.2.0.1 (RC1) Build ID: fcbcb4963bda8633ba72bd2108ca1e802aad557d CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Locale: es-MX (es_MX) on Windows 10 Versión: 5.2.0.0.beta2 Id. de compilación: a83fc06803e11f27e95c809fdfacbbd0377ff7d0 Subprocesos de CPU: 8; Versión de SO: Windows 6.2; Renderizado de IU: predeterminado; Configuración regional: es-MX (es_MX) Version: 5.2.0.0.beta1 Build ID: 1e9933ef611c66bcded94b84052543c78cf1c223 CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Locale: es-MX (es_MX) Version: 5.2.0.0.alpha1+ Build ID: 13a52d0a718825f82f3d4b1684bf86b812fce1f2 CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; TinderBox: Win-x86@62-merge-TDF, Branch:MASTER, Time: 2016-05-22_22:59:44 Locale: es-MX (es_MX) Version: 5.3.0.0.alpha0+ Build ID: 0c1767d9466adf0729eb8e1f43ddb80a31886898 CPU Threads: 8; OS Version: Windows 6.19; UI Render: default; TinderBox: Win-x86@39, Branch:master, Time: 2016-06-21_01:16:33 Locale: es-MX (es_MX) on Windows 10 Works OK in LO Version: 5.1.4.2 Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a CPU Threads: 8; OS Version: Windows 6.2; UI Render: default; Locale: es-MX (es_MX) in Windows 10 and LO Version: 5.0.6.3 Build ID: 490fc03b25318460cfc54456516ea2519c11d1aa Locale: es-MX (es_MX)
Created attachment 125864 [details] Test file
Reproducible also in OpenSUSE Leap 42.1 Version: 5.2.0.0.beta2+ Build ID: 97b0b8c1f7310c3ca85229a9455decf35e08811f CPU Threads: 8; OS Version: Linux 4.1; UI Render: default; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:libreoffice-5-2, Time: 2016-06-20_22:49:47 Locale: es-MX (es_MX.UTF-8)
Change to OS All
Hi @Robert, maybe I don't understand how to do, but I'm not able to reproduce. Win10x64 Version: 5.1.4.2 (x64) Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; Locale: es-ES (es_ES) Have you test changing the state of OpenGL?
(In reply to m.a.riosv from comment #4) > Hi @Robert, maybe I don't understand how to do, but I'm not able to > reproduce. > Win10x64 > Version: 5.1.4.2 (x64) > Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a > CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; > Locale: es-ES (es_ES) > > Have you test changing the state of OpenGL? I have Windows 10 and OpenGL is disabled, but in 5.1.4.2 (x86) released today, the problem is not present. Only in 5.2 and 5.3
Ok, reproducible. Win10x64 Version: 5.3.0.0.alpha0+ Build ID: 5bd5baff3f2a55bc2d84e1e352a00dd6969394e3 CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL; TinderBox: Win-x86@39, Branch:master, Time: 2016-06-23_10:58:15
Also with: Version: 5.2.0.1 (x64) Build ID: fcbcb4963bda8633ba72bd2108ca1e802aad557d CPU Threads: 4; OS Version: Windows 6.19; UI Render: GL;
Adding regression and bibisectRequest, likely will be the same result as for bug 100573.
(In reply to Aron Budea from comment #8) > Adding regression and bibisectRequest, likely will be the same result as for > bug 100573. Yes the same commit caused this, see "tdf#46637 - Make partially visible cells fully visible on mouse click" caused this regression.
*** This bug has been marked as a duplicate of bug 100573 ***