<div dir="ltr">I doubt my word would carry any more weight.<div><br></div><div>Instead, get the Theme developers who are actually *using* Masonry, who would be impacted by (i.e. benefit from) the change to comment in the ticket, confirming their desire and intent to use Masonry 3.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 23, 2013 at 6:30 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">@chip, yep the issue is a outdated core bundled version of core, with a new version that is not backwards compatible. As far as I can tell the only things that are broken by the upgrade in core by a Masonry 3 are the footer widgets in core bundled themes.<div>
Nacin, and I think Helen as well, consider that a show-stopper. If you disagree with them on this, could you please say so in the ticket? I know lead developer trumps theme review admin, but theme review team admin should carry more weight then random guys (ie me and Rohit.) Thanks.</div>
</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Nov 23, 2013 at 5:37 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">And here's the rub: Theme developers have been wanting/trying to use the latest version of Masonry, and we have been requiring them to use the core-bundled version. (See previous mail-list discussions regarding Masonry.)<div>
<br></div><div>I say: provide a reasonable timeframe, and make the change. The problem (apparently - I'm also not a jQuery person) is that WordPress core bundles an outdated version of Masonry. We shouldn't compound that issue by forcing it to remain in core. If a bridge script can be written, all the better. But it shouldn't be a showstopper for getting Masonry 3 into core.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Sat, Nov 23, 2013 at 4:18 PM, Otto <span dir="ltr"><<a href="mailto:otto@ottodestruct.com" target="_blank">otto@ottodestruct.com</a>></span> wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div class="gmail_extra"><div class="gmail_quote">On Sat, Nov 23, 2013 at 2:36 PM, Josh Pollock <span dir="ltr"><<a href="mailto:jpollock412@gmail.com" target="_blank">jpollock412@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Would anyone's theme experience a similar issue? Probably. Is that a valid objection to upgrading in core?</div>
<div></div></div></blockquote></div><br></div></div><div class="gmail_extra">Probably.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Is what nacin suggested about writing a back-compat wrapper possible? I'm not a javascript guru and I have no idea what the changes in masonry are. But if an add-on of some type can be made to fix compatibility breaks, then it's more likely to get in.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra">The short end of it is that if at all possible, core upgrades cannot break people's websites. If somebody is using Masonry 2 and upgrading core to Masonry 3 will break that site, then Masonry 3 just ain't gonna go in. But if a "masonry-fix" script can be added to prevent that breakage, well, that will go over much better.</div>
<span><font color="#888888">
<div class="gmail_extra"><br></div><div class="gmail_extra">-Otto</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></font></span></div>
<br></div></div><div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>