<html>
<head>
<base href="https://bugs.documentfoundation.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - new documents fail ODF validation with Error: unexpected attribute "draw:fill""
href="https://bugs.documentfoundation.org/show_bug.cgi?id=103602#c46">Comment # 46</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - new documents fail ODF validation with Error: unexpected attribute "draw:fill""
href="https://bugs.documentfoundation.org/show_bug.cgi?id=103602">bug 103602</a>
from <span class="vcard"><a class="email" href="mailto:vmiklos@collabora.com" title="Miklos Vajna <vmiklos@collabora.com>"> <span class="fn">Miklos Vajna</span></a>
</span></b>
<pre>We have this trade-off that we either conform to the spec fast or we care about
existing documents, where users typically expect full backwards-compatibility.
I believe we can't meet both requirements at the same time. My understanding is
that we already write valid ODF in the non-extended case, and we can phase out
the invalid ODF output over time in the extended case as well. So the status
quo looks like a reasonable compromise to me.
Next time perhaps we can detect & fix such problems earlier. I think this was
introduced in commit 7d9bb549d498d6beed2c4050c402d09643febdfa (Related:
#i124638# Second step of DrawingLayer FillAttributes..., 2014-06-02), and now,
6 years later, we can't just fix such things instantly.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>