<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: Buttons to toggle border lines on/off in table properties border dialog" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143249#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - UI: Buttons to toggle border lines on/off in table properties border dialog" href="https://bugs.documentfoundation.org/show_bug.cgi?id=143249">bug 143249</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=143249#c2">comment #2</a>) > Sure, this would be a solution. And it has the advantage to be a bit more > a11y-friendly. But better keep all aspects of a redesign together in one > ticket. No objection to a single ticket. The problem is more my hesitation to write it down in a way people don't get overwhelmed or confused. The logic of the dialog is already that confusing (for me), that the attempt to write it down (in a single report) becomes 'as confusing' as the incidents experienced . And me lacking the right vocabulary to be very precise about what the problem is, how and when it occurs (and cases where it does function) doesn't help.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>