Table style of the source table changes to the one of the target table if there is mismatch between number of rows
Steps to Reproduce:
1. open the attachment
2. Select full table or only the content
3. Drag it into the red one
4. The blue table will convert to red
The blue table will convert to red
User Profile Reset: No
Build ID: 1b21ff86effe58ae368457de8fec654ba4c8edd9
CPU threads: 4; OS: Windows 6.3; UI render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2018-07-30_03:13:35
Locale: nl-NL (nl_NL); Calc: CL
Created attachment 143843 [details]
Note: Can't be fixed by using undo
No repro with
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
No repro with
Build ID: 78223678b7513ffe46804cb08f2dc5bc899b2bab
CPU Threads: 4; OS Version: Windows 6.29; UI Render: default;
Locale: nl-NL (nl_NL); Calc: C
Bibisected with win32-6.1 to https://cgit.freedesktop.org/libreoffice/core/commit/?id=137c38a1ba01c51c421f695e1558d2c1499c6627
tdf#117189 Fix table InsertRow redo
Adding Cc: to Jim Raykowski
Bibisecting notes: a hanging bug in the history made things slightly tricky so I had to do this sort of thing a few times:
git log --reverse --pretty=%H master | grep -A 1000 $(git rev-parse HEAD) | tail -n1 | xargs git checkout
to move forward from the oldest commit in the repo.
Revert of tdf#117189 sent to gerrit to fix this.
(In reply to Jim Raykowski from comment #6)
> Revert of tdf#117189 sent to gerrit to fix this.
What about the initial bug?
(In reply to Telesto from comment #7)
> (In reply to Jim Raykowski from comment #6)
> > Revert of tdf#117189 sent to gerrit to fix this.
> What about the initial bug?
It will need to be reopened after revert is merged. The reviewers comment was that this patch was very plausible that this should fix things but alas it seems not so :(
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!