1. Create a table of 'X' number of columns, 'Y' number of rows. Highlight all columns; select center data. The first cell of the last column is not centered, or highlight all rows; selected center data. The last cell of the first column is not centered. 2. Create a table of 'X' number of columns, 'Y' number of rows. Create a second table of 'X' number of columns, 'Y' number of rows. Merge the two tables by deleting the blank line between the two tables. Now highlight one of the columns. Notice the highlighted column does not extend beyond the first table. Once the tables have been merged, they should become one table. 3. Using the two tables in problem 2. You cannot highlight rows beyond the first table. 4. Create a numbered list (say 3 numbers). Now highlight the wordage of the first number. Cut this information and paste it into any column of a table. Notice the line is copied with the next number of the numbered list. Deleting the number does not let the copied information go to the start of the column. 5. Let's say you have a table of ten columns and you decide to delete the first five columns. When the five columns are selected and the delete command is given. The selected columns are not deleted but merged into the sixth column. The first column is now the size of the first six columns. This is not right.
This is not a proper way to report. Each issue must have a separate bug and similar bugs are related via See Also. But rule of thumb is search before reporting, did you do it for each issue? Single report must have reproducible steps and better minimal sampke attached, so that tester doesn't have to recreate each time.
Also, I don't thick tables can be merged, although they appear joined.
Dear Don Meinsen, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Don Meinsen, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp