<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN FILESAVE IMPORT Conditional formatting: xls file with a lot of Conditional formatting freeze Calc when opening Styles sidebar" href="https://bugs.documentfoundation.org/show_bug.cgi?id=100894#c15">Comment # 15</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - FILEOPEN FILESAVE IMPORT Conditional formatting: xls file with a lot of Conditional formatting freeze Calc when opening Styles sidebar" href="https://bugs.documentfoundation.org/show_bug.cgi?id=100894">bug 100894</a> from <a class="email" href="mailto:ungift-ed@ya.ru" title="Maxim Britov <ungift-ed@ya.ru>"> Maxim Britov</a> <pre>(In reply to Luke from <a href="show_bug.cgi?id=100894#c14">comment #14</a>) > My 2 cents: This file is also broken under both Excel 2013 and 2016. It > seems like it was possibly created programmatically or by someone > intentionally trying to break Excel. This file uses overlapping conditional > formats, a feature we don't properly support. See <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - FILEOPEN: XLSX - Conditional Formatting rules not compatible with Excel's" href="show_bug.cgi?id=91654">Bug 91654</a>. > > Wouldn't it make more sense to focus on improving interoperability with real > world files, rather than optimizing a feature we don't even support properly? Please read comments. Initial comment for example. File from real user, personal data dropped from tables. Excel 2003. Converted and saved from Office 365 from my Android. I will attach it.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>