Removing a table border in the Table Properties menu (user defined) needs three clicks. But I'm not seeing any purpose for the second click? Just toggling on/off seems to be enough (to me).
Steps to Reproduce:
1. Open attached file
2. Select the top row (blue border)
3. Right click -> Table Properties
4. Go to tab borders
5. A single click on (blue) line in the line arrangement preview (select)
6. A second single click on the same line again -> 'blue line changes to grey'
7. A third single click in the gray line -> line disappears
Three clicks for removing a table border in the line arrangement preview
Two clicks for removing a border line
User Profile Reset: No
Build ID: 274ecb49b70b3f01d47546e3b44317946c106042
CPU threads: 4; OS: Windows 6.2; UI render: default;
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2017-05-05_22:45:07
Locale: nl-BE (nl_NL); Calc: single
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:45.0) Gecko/20100101 Firefox/45.0
"When the selected cells have different styles of border the User-defined area shows the border as a gray line. You can click on the gray line to choose a new border style (first click), leave the border as it is (second click) or delete the border (third click)."
Could it be made somehow more obvious? Personally, this is news to me. Let's circle this through the UX meatgrinder.
Mean reason for my confusion is that I expected that the second click meant, back to default border. I was certain that the second click removed the blue border because it didn't show up anymore.
I would keep the less known property of the grey line for inherited properties first to show this to users. Otherwise you always click once and never see the undetermined state. -> WFM - but lets see if others disagree
PS: As there is no attachment simply create a table and set the border color of some cells.
Created attachment 133193 [details]
*** Bug 108276 has been marked as a duplicate of this bug. ***
(In reply to Heiko Tietze from comment #3)
> WFM - but lets see if others disagree
No further opinion, let's keep it.
*** This bug has been marked as a duplicate of bug 139018 ***