Description: UI: The table properties table border tool is counter-intuitive (lacking feedback) Steps to Reproduce: 1. Open attachment 173439 [details] 2. Select the orange area 3. Menu Table -> Properties -> Borders tab 4. Go to table width field and scroll up to say 2 pt.. Notice all borders are affected 5. Scroll down again to 0.05 pt 6. Click on a border (it's will be selected state (gray) 7. Scroll width up again to 2.75 pt or so (notice only the selected border is affected) 8. Scroll with down again (to 0.05 pt) [ or skip if you want visibility for step 9) 9. Click another border (there is no selected state, the new setting is applied automatically. However no way to 'tell that' (bug 143248). I assumed it would be in selected state like in step 6. 10. Press OK 11. Menu Table -> Properties -> Borders tab (with same selection) 12. Go to table width field and scroll up to say 2 pt (notice nothing is happening, caused by custom borders. But no way to tell that 13. Clicking select all border and inner lines fixes the behaviour (however will erase all different settings again for inner border if existend) Actual Results: The table border tool is far from easy to use. Why it works this way can be explained. But it's pretty complex (and lacking feedback) Expected Results: Well this not an easy topic. LibreOffice does behave how Word (2003) does. Not winning awards, IMHO. * Maybe a way to change similar borders in tandem? * Showing which borders are selected. Apparently all are at step 4 (but that's not visible). A single border has selected 'border' but full table hasn't? Reproducible: Always User Profile Reset: No Additional Info: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: bd2f2273d83dcca43eb6b465308707efd45e7adf CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Sorry for 'pollution'. However the table border thingy surely unpractical Explaining why it's broken and in which way it's broken and how the improve it is quite a thing. As this really depends on 'use case'. So certain workflows this actually works out pretty well, but if you do it somehow 'different' you get into a fight.
(In reply to Telesto from comment #1) > As this really depends on 'use case'. So certain workflows this actually > works out pretty well, but if you do it somehow 'different' you get into a > fight. Exactly, and changing breaks someone's workflow. I suggest to close all tickets around border attributes and focus on a new interaction at one enhancement ticket. Happy to come up with a mockup then.
*** This bug has been marked as a duplicate of bug 143249 ***