Description: Merging cells with outside border only would make the right (and bottom) border disappeared. Different results from different border type. For some border type the right and bottom border would disappear after merging; for some other (thicker) border type would make right border disappeared, but bottom border still there just thinner. Steps to Reproduce: 1. Start a new Calc spreadsheet 2. Mark a range (say, B3:F12) 3. Set up a border with outside only (no inner grid) 4. Merge these cells Actual Results: The right (and sometimes bottom also) border would disappear Expected Results: The border should be complete Reproducible: Always User Profile Reset: No Additional Info: Earliest tested version: 版本 3.6.7.2 (組建 ID：e183d5b) Should be inherited from OOo
Created attachment 187470 [details] test border after merging cells
Seems because of the right border, it's inherited from the first cell in the merged range, not from the last.
After checking the last month's unconfirmed bugs, it was found out that the bug report is not duplicate. As a result of of reproducing the bug with stable and master build, it has been confirmed that the bug report is correct. Actual and expected results are different as mentioned by Franklin Weng. Merging cells with outside border only would make the right (and bottom) border disappeared. Therefore the status has been changed to "NEW" from "unconfirmed".
(In reply to Franklin Weng from comment #0) > Actual Results: > The right (and sometimes bottom also) border would disappear Right and bottom sides are the corresponding left and top sides of the adjacent surrounding cells. BTW, the "_sometimes_ bottom also" comment is just a graphical glitch; simply scroll down and up again so to refresh the screen and you should see that the bottom border is not there, just the same as the right side border of the merged range. Now, if the right and bottom borders are kept after merging, some users will report that the borders of the surrounding cells are lost, and such behavior would be unexpected.
Dear Franklin Weng, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
(In reply to QA Administrators from comment #5) > Dear Franklin Weng, > > 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. > Still reproducible in Version: 25.2.2.2 (X86_64) / LibreOffice Community Build ID: 7370d4be9e3cf6031a51beef54ff3bda878e3fac CPU threads: 4; OS: Linux 6.8; UI render: default; VCL: kf5 (cairo+xcb) Locale: zh-TW (zh_TW.UTF-8); UI: zh-TW Calc: threaded
Excuse me, is Bug 167510 the same as this one?