<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">From: mrmist <<a href="mailto:listswpdocs@mist.org.uk">listswpdocs@mist.org.uk</a>><br>Personally I would vote for culling these at the next release,<span class="Apple-converted-space"> </span><br>regardless of whether the compatible with feature is implemented by then<span class="Apple-converted-space"> </span><br>or not.<br><br>Either that, or change the format of the next set of compatibility pages<span class="Apple-converted-space"> </span><br>so that they are like the automatic upgrade host compatibility pages -<span class="Apple-converted-space"> </span><br>IE non-linked.<br><br>Or just make them a set of "INcompatibility pages" to list<span class="Apple-converted-space"> </span><br>themes/plugins with known issues. ;)<br></span></blockquote><br></div><div>Big +1. Jane</div><br></body></html>