[Libreoffice-ux-advise] [Bug 87787] New: Improve cell border assignment

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=87787

            Bug ID: 87787
           Summary: Improve cell border assignment
           Product: LibreOffice
           Version: Inherited From OOo
          Hardware: Other
                OS: All
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: ux-advise
          Assignee: libreoffice-bugs at lists.freedesktop.org
          Reporter: philipz85 at hotmail.com
                CC: libreoffice-ux-advise at lists.freedesktop.org

Not sure if this should be considered a bug or an enhancement, bug setting cell
borders in writer and calc are a major pain because cells that share the same
border visually can have different border settings and these border dont play
nicely together.

For writer, if you insert a table of 3x3, and in cell B2 you set the borders to
none, the left and bottom borders show as transparent but not the top and
right. I'm assuming the way the cells are being draw to make up the table maybe
causing it to look like this, as unfortunately there isnt a means for me to
open up the cell properties and see exactly what is going on. In order to
achieve what is intended, a user will likely have to jump through many hoops to
get the way it should be.

For calc, select a number of cells (e.g. C7:F16), and set their inner and outer
borders, then select one of the cells (e.g. E12) in the changed cells and set
its borders to none. You wont visually see a difference because the cells
around it all have their borders on. So in order to achieve what is intended, a
user will have to go to each of the 4 cells around it, open up the formatting
cell dialog and disable the related sides.

So the simple solution is that when a cell border is set or unset in any manner
(border width, style, color, etc), that its neighboring cells must also be set
or unset in the same way.

-- 
You are receiving this mail because:
You are on the CC list for the bug.