Repeated, completely off-topic but entirely related, Microsoft has produced a site at <a href="http://modern.ie">http://modern.ie</a> that makes testing IE as simple as possible (providing VHDs for Mac and Linux as well). Just in case anyone missed it :)<br>
<br><div class="gmail_quote">On 1 February 2013 08:42, Edward Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@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>As long as the reviewer is using a "modern" browser in their process I am not overly concerned they review the theme in multiple browsers. For the most part, what we as reviewers are looking at will be apparent no matter which browser the theme is being viewed with; and, also, visual issues with the theme tend to fall mostly to aesthetics which also (for the most part) are not requirements that need to be met for approval.<br>
<br></div>Now, all that being written, if a reviewer finds that in a specific browser something doesn't *look* right (but does *work* correctly) it is strongly recommended the reviewer let the theme author know so they can address that issue if they choose to.<span class="HOEnZb"><font color="#888888"><br>
</font></span></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div>Edward Caissie<br>aka Cais.</div></font></span><div><div class="h5">
<br><br><div class="gmail_quote">On Fri, Feb 1, 2013 at 3:08 AM, Paul Appleyard <span dir="ltr"><<a href="mailto:paul@spacecat.com" target="_blank">paul@spacecat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"><div>
On 1/02/2013 5:53 PM, Alex Watson wrote:<br>
<blockquote type="cite">
<div> I think we should recommend that the theme works in all
modern browsers. Microsoft have just launched <a href="http://www.modern.ie/" target="_blank">http://www.modern.ie</a> making
it a lot easier to test in IE. Being a web developer I have a
Browserstack account, as making sure my work is cross browser
compatible is essential to me. Besides, nowadays its a lot
easier to make sure sites work in IE, compared to the days of
IE6!</div>
</blockquote>
<b><br>
</b></div><i>Agreed; but once again it comes down to the reviewer testing
it in all modern browsers.</i><div><br>
<br>
<blockquote type="cite">
<div><br>
</div>
<div>Btw the guy who built the theme has got back to me and says
that the theme does not support IE9+. (odd, as i notice he does
include the html5shiv.js, so he must be thinking about IE at
least. Anyway I am yet to actually test his site in IE) As a
theme reviewer, regardless of the guidelines I will be testing
in all modern browsers anyway. If a site totally breaks in IE9+
(perhaps even in IE8) then I'd have concerns.</div>
</blockquote>
<br>
</div><i>So 'does not support IE9+' would mean all IE versions - unless
for some weird reason it works in, say, IE8 .. but I guess what
he's saying is that he doesn't expect it to work properly in IE.
Out of curiosity, what are these features that IE can't handle?</i><br>
<br>
<blockquote type="cite">
<div><br>
</div>
<div>Alex</div><span><font color="#888888">
</font></span></blockquote><span><font color="#888888">
<br>
<i>Paul</i></font></span><div><div><br>
<br>
<br>
<blockquote type="cite">
<div>
<div><span style="color:rgb(160,160,168)"><br>
</span></div>
<div><span style="color:rgb(160,160,168)">On Friday, 1
February 2013 at 07:13, Paul Appleyard wrote:</span></div>
</div>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px">
<span>
<div>
<div>
Any new browser-centric requirements would hit a
limitation on what browser the reviewer uses, or can use.
So there's a built-in restriction on browser support, in
that it must support the reviewer's browser, which is very
likely a recent Chrome or Firefox iteration.<br>
<br>
I guess it (theme-specified browser requirements) would
also come in to play as an issue if the theme author is
implementing some pretty specific Javascript or HTML5
(some advanced canvas manipulation stuff for example,
although Excanvas helps there too with IE7/8) And that's
bleeding in to plugin territory, really.<br>
<br>
To sum up: If it doesn't break in a way to fail on
existing guidelines, let it be. Therefore, the only
amendment to review guidelines would be that testing be
done in an up-to-date browser; is that requirement in
there already?<br>
<br>
Paul<br>
<br>
<div>On 1/02/2013 2:43 PM, Justin Tadlock wrote:<br>
</div>
<blockquote type="cite">
<div>
I'm pretty much in agreement with Chip.<br>
<br>
My personal rule in regards to IE is to support the 2
latest versions, which are currently 9 and 10.<br>
<br>
<div>On 1/31/2013 7:03 PM, Chip Bennett wrote:<br>
</div>
<blockquote type="cite">
<div>
<div dir="ltr">I have no problem with it. A
properly developed and designed Theme should
have minimal IE issues anymore, anyway.
<div><br>
</div>
<div>I don't "support" IE with my
Theme, either. I can't; I use Linux, and thus
have no way of even *running* IE.</div>
<div><br>
</div>
<div>Doing something that actively
*excludes* IE (or any other browser) would
certainly not be acceptable; but developing a
standards-compliant Theme, and opting not to
jump through hoops for IE? Meh; doesn't bother
me all that much.</div>
</div>
<div><br>
<br>
<div>On Thu, Jan 31, 2013 at 7:20 PM, Edward
Caissie <span dir="ltr"><<a href="mailto:edward.caissie@gmail.com" target="_blank">edward.caissie@gmail.com</a>></span>
wrote:<br>
<blockquote type="cite">
<div>
<div dir="ltr">
<div>
<div>Flatly not supporting one of the
most commonly found browsers (not
necessarily used but it does come
with Windows) is not a very good
idea; and although we do not have
any specific guidelines in place I
think if a Theme Author is going
that route something that
significant should be in the Theme
description.<br>
<br>
</div>
As it is, you would be better served
by asking the Theme author to explain
that statement before making any
assumptions. As noted, it may only be
that they are supporting current
versions of IE and simply left off the
version number in their readme file.<br>
<br>
</div>
Myself, for general distribution themes,
I only support current (or one version
back at the most) browsers. I don't
state the actual version only making
reference to the browser being current.
Of course, client work is generally
different but those "rules" do not
necessarily apply here.<span><font color="#888888"><br>
</font></span></div>
<div><span><font color="#888888"><br clear="all">
<div>Edward Caissie<br>
aka Cais.</div>
</font></span>
<div>
<div> <br>
<br>
<div>On Thu, Jan 31, 2013 at 7:12
PM, John Heimkes IV <span dir="ltr"><<a href="mailto:john@heimk.es" target="_blank">john@heimk.es</a>></span>
wrote:<br>
<blockquote type="cite">
<div>
<div style="word-wrap:break-word">That's
a great question, actually.
I'd like to know what the
general consensus is on this
matter. Don't worry about
being fussy. I've been doing
front-end for many years.
So, I totally get it.
<div> <br>
</div>
<div>My personal opinion is
if they're not going to
support certain browsers
(aka, the browsers most of
us web developers have to
support on a daily basis),
the author <i>should</i>
make it known up front -
especially in the CSS file
for good documentation
purposes. Some sort of
clarification from the
author would be nice in
this case. Maybe they're
just not supporting older
versions of IE and it
looks fine in IE10, and
maybe even IE9.</div>
<div><br>
</div>
<div>Anyway, I hope someone
else has a better answer!</div>
<div><br>
</div>
<div>Thanks,</div>
<div>John Heimkes IV</div>
<div>
<div>
<div><br>
<div>
<div>On Jan 31,
2013, at 6:03 PM,
Srikanth Koneru
<<a href="mailto:tskk79@gmail.com" target="_blank">tskk79@gmail.com</a>>
wrote:</div>
<br>
<blockquote type="cite">
<div>
<div dir="ltr">Since
IE has at
least 30%
browser share,
I think theme
has to support
it.<br>
</div>
<div><br>
<br>
<div>On Fri,
Feb 1, 2013 at
5:31 AM, Alex
Watson <span dir="ltr"><<a href="mailto:alex@alexwatson.co.uk" target="_blank">alex@alexwatson.co.uk</a>></span>
wrote:<br>
<blockquote type="cite">
<div>
<div>Hi
everyone!</div>
<div><br>
</div>
<div>So I'm
reviewing my
first theme,
and a few mins
into it I find
this in the
readme.txt:</div>
<div><span style="font-family:monospace;white-space:pre-wrap"><br>
</span></div>
<div><span style="font-family:monospace;white-space:pre-wrap">*
NOT SUPPORTED
on Internet
Explore *</span></div>
<div><span style="font-family:monospace;white-space:pre-wrap"><br>
</span></div>
<div><span style="white-space:pre-wrap">Is
that okay? Are
themes allowed
to be built
and not work
in IE at all?
It's probably
the fussy web
developer side
of me coming
out here, as
everything I
do has to work
in IE8+ :)
I've not got
so far as to
have tested it
in IE yet, but
are we even
required to do
cross browser
testing? I
think we
should, but I
can't see that
in the review
guidelines
anywhere.</span></div>
<div><span style="white-space:pre-wrap"><br>
</span></div>
<div><span style="white-space:pre-wrap">Anyway,
please let me
know if I'm
just being too
fussy here!
(and sorry if
this has been
asked before
but I just
joined this
mailing list a
couple of days
ago)</span></div>
<div><span style="white-space:pre-wrap"><br>
</span></div>
<div><span style="white-space:pre-wrap">Many
thanks</span></div>
<span><font color="#888888">
<div><span style="white-space:pre-wrap"><br>
</span></div>
<div><span style="white-space:pre-wrap">Alex</span></div>
</font></span><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>
</div>
</blockquote>
</div>
<br>
</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>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</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>
</div>
</blockquote>
</div>
<br>
</div>
</div>
</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>
</div>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</div>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</div>
</blockquote>
<br>
</div>
<div>
<div>_______________________________________________</div>
<div>theme-reviewers mailing list</div>
<div><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a></div>
<div><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a></div>
</div>
</div>
</span> </blockquote>
<div> <br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
theme-reviewers mailing list
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a>
</pre>
</blockquote>
<br>
</div></div></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>