<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Black is set as New color in Area tab when a table with multiple colors in its cells is selected" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111769#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Black is set as New color in Area tab when a table with multiple colors in its cells is selected" href="https://bugs.documentfoundation.org/show_bug.cgi?id=111769">bug 111769</a> from <a class="email" href="mailto:zolnaitamas2000@gmail.com" title="Tamás Zolnai <zolnaitamas2000@gmail.com>"> Tamás Zolnai</a> <pre>> In Writer, when you open the table properties dialog, you are modifying the > table-level properties and can set a single background color. In Impress, > when you open the table properties dialog, you are opening a properties > dialog based on what is currently selected and are not modifying table-level > properties, which is why the background tab messes up when cells have > multiple colors. No, you are wrong here. Writer table properties dialog works the same. When cells are selected it uses the selected's cells color. So I still think it's the best to be consistent here and recognize ambigous fill attributes as "None". Also this crossed-out image think might be harder to implement, but of course you can implement it. If you are stick with your idea (under you, I mean UX team), then better to remove easyhack keyword and I guess somebody can implement it in the UX team.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>