Steps to reproduce: 1. Open attachment 131273 [details] from bug 106043 2. Click on 'Start selection here' 3. Use select all three times -> Nothing is selected ( or the selection vanished after a few seconds ). Instead, content of both tables should be selected Reproduced in Version: 7.1.0.0.alpha0+ Build ID: ff508f6d8a3e58d29e9e7622006a7103fb0a2849 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: x11 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=c56bf1479cc71d1a2b0639f6383e90c1f7e3655b author Miklos Vajna <vmiklos@collabora.com> 2019-09-16 21:15:28 +0200 committer Miklos Vajna <vmiklos@collabora.com> 2019-09-17 08:57:15 +0200 commit c56bf1479cc71d1a2b0639f6383e90c1f7e3655b (patch) tree 3db679971be5be40d2f737202de6b8106dc1d53c parent 813cca94cd3a08d98c09fc7c34afddd02dc912ce (diff) tdf#105330 sw: fix lost cursor on undoing nested table insert Bisected with: bibisect-linux64-6.4 Adding Cc: to Miklos Vajna
also reproduced with attachment 92052 [details] from bug 73616
Hmm, I don't think this ever worked. Yes, it "worked" after e4509eea8fc7c07ddff48edf0d4c015c2663d896 and before c56bf1479cc71d1a2b0639f6383e90c1f7e3655b but only with serious side-effects. So yes, it makes sense to fix this at some stage, but we need to came up with a plan on how to do these notifications in some better way. Clearly whatever you do (you only do it conditionally or unconditionally), currently you have problems. Till a better condition is found, it makes sense to have the state that was there forever, not replacing an old problem with a new one. Adjusting keywords accordingly.
So this issue is only happening with GTK3, in the summary I was wrong with the about LibreOffice info. @Caolán, I thought you might be interested in this issue
ok, no gtk3 only, can happen with gen but with gtk3 it happens all the time, with gen, sometimes...
Issue fixed by https://git.libreoffice.org/core/commit/6f1e02c96b887750f974c187a82ecd6236e6a435 Closing as a dupe of bug 135682 *** This bug has been marked as a duplicate of bug 135682 ***