<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Recommended Browsers for LDS.org Tools</title>
		<description>Discuss Recommended Browsers for LDS.org Tools</description>
		<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools</link>
		<lastBuildDate>Tue, 18 Jun 2013 19:27:27 --700</lastBuildDate>
		<generator>JComments</generator>
		<atom:link href="http://tech.lds.org/component/jcomments/feed/com_content/531/10" rel="self" type="application/rss+xml" />
		<item>
			<title>Sperry Hope says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-2610</link>
			<description><![CDATA[Just another note on this issue. Looks like IE10 has issues as well. I use Chrome for most of my browsing but have to use IE for part of my job. I get a nice message on some of the tools to upgrade my browser but I am running the latest released IE Version available.]]></description>
			<dc:creator>Sperry Hope</dc:creator>
			<pubDate>Wed, 05 Jun 2013 12:06:45 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-2610</guid>
		</item>
		<item>
			<title>Aaron Barker says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1915</link>
			<description><![CDATA[I'm late to the party, but thought I'd add to the discussion. I'm the front-end lead for the content portions of LDS.org (so not calendar, directory, etc). As such, this is speaking for those portions, not others (unless specified below). We do support IE8, but do not expect that it will have a perfect experience. Users should be able to consume all content, but occasionally it may not be pretty. One of my happiest days will be when we drop IE8. IE9 is a decent browser and we don't have to jump through many hoops for it. IE7 was dropped about a year ago (another happy day). It currently generates less than 1% of our traffic. Due to that low usage it has been dropped for ALL lds.org properties (including calendar, directory, etc). We will of course continue to support IE. Which versions we support is what will change over the years. I anticipate IE8 will be dropped next year as a result of reduced usage (currently around 10%)]]></description>
			<dc:creator>Aaron Barker</dc:creator>
			<pubDate>Thu, 01 Nov 2012 07:02:37 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1915</guid>
		</item>
		<item>
			<title>Jason Bowne says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1856</link>
			<description><![CDATA[As a foundation testing should happen on 4 browsers (IE, chrome, Firefox, safari). Hopefully HTML 5 is the future of church websites as it is a standard all 4 browsers will support without needing to have different code. I just got a Microsoft surface and love it, however unless chrome, Firefox, or safari write an app for the Windows store I won't be able to run it on Windows RT. Most church websites seem to work fine on IE10. Debating apple, android, Windows is like trying to debate what blade of a pair of scissors is more important. It is a multi device / multi os / multi browser world - lets accept that and move on.]]></description>
			<dc:creator>Jason Bowne</dc:creator>
			<pubDate>Sat, 27 Oct 2012 22:50:19 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1856</guid>
		</item>
		<item>
			<title>S. Michael Convey says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1840</link>
			<description><![CDATA[Gary, that is exactly why we sent an email to all members of our stake explaining the situation, referencing this blog post, and providing links to the recommended browsers. Installing one of the recommended browsers is very simple: click on a link and it installs and your done.]]></description>
			<dc:creator>S. Michael Convey</dc:creator>
			<pubDate>Tue, 23 Oct 2012 13:00:58 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1840</guid>
		</item>
		<item>
			<title>Gary Miller says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1837</link>
			<description><![CDATA[As a consumer and a computer user, I can assure you that the average home user is still using IE as a browser. This is due to the fact that windows is still the main operating system on computers purchased in the local store. And while Microsoft is going to stop supporting XP come next spring, XP will still be used by many home computer users due to the cost of upgrading. And these people will still be using IE. While I know to use a different browser, its only because I'm frequent the tech forms that I knew what to do then the calendar went wacky using IE. However, I afraid the average member trying to use the calendar system will not know this. Will not know who to ask to fix the problem, and will just not use the calendar at all. Mind you I'm talking about the average home computer user, not the clerk computers.]]></description>
			<dc:creator>Gary Miller</dc:creator>
			<pubDate>Tue, 23 Oct 2012 10:09:50 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1837</guid>
		</item>
		<item>
			<title>Doug Merrill GSC says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1783</link>
			<description><![CDATA[Software such as Google Chrome does not need approval to install onto a MLS Clerk computer. The instructions (mls.lds.org) for installing MLS onto a Windows 7 computer specifically says "Use the links provided to download MLS, the Local Unit Security Software, the Computer Management Software, and any Additional Local Unit Software you prefer", on page 3. On page 4, under Optional Items, it says "Install the additional applications you downloaded earlier such as Adobe Reader, Open Office, CutePDF, Google Chrome, and the Record-Keeping Training Installers.". Based on this, I believe the division on what needs stake approval is based on software licensing requirements. Best Practice though is; if you have a question, ask the Stake Clerk to discuss it with the Stake President. I hope this helps]]></description>
			<dc:creator>Doug Merrill GSC</dc:creator>
			<pubDate>Fri, 19 Oct 2012 08:06:59 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1783</guid>
		</item>
		<item>
			<title>S. Michael Convey says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1758</link>
			<description><![CDATA[Thanks, I didn't realize that. I'm not surprised. I gave up all Apple products a couple of years ago. This is just another reason to not purchase their products.]]></description>
			<dc:creator>S. Michael Convey</dc:creator>
			<pubDate>Thu, 11 Oct 2012 16:54:26 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1758</guid>
		</item>
		<item>
			<title>Dan Jones says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1757</link>
			<description><![CDATA[Sadly, Chrome on iOS isn't really Chrome. Because of the restrictions that Apple places on apps that can be approved to the App Store, browsers must still use the stock rendering and Javascript engine. What this effectively means is that on iOS, Chrome is really just Mobile Safari with a Chrome façade. It has many of the features of Chrome for Android, but it's not near as fast, nor as secure. In fact, because of optimizations done on Mobile Safari, Chrome for iOS is much slower than Mobile Safari.]]></description>
			<dc:creator>Dan Jones</dc:creator>
			<pubDate>Thu, 11 Oct 2012 16:45:41 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1757</guid>
		</item>
		<item>
			<title>Dan Jones says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1755</link>
			<description><![CDATA[There are always exceptions, and while I seriously doubt that you are, it's certainly a possibility that in the very limited case of your particular computers, Safari is faster and more secure, but you would be the extreme exception, as many tests have proven.]]></description>
			<dc:creator>Dan Jones</dc:creator>
			<pubDate>Thu, 11 Oct 2012 16:41:59 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1755</guid>
		</item>
		<item>
			<title>Marilyn Kay Wiley Howard says:</title>
			<link>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1754</link>
			<description><![CDATA[Dan Jones - That is not an accurate statement. We have Dell and HP systems, we have all 3 browsers I mentioned and Safari has proven to be the fastest, most secure except for one task that we do using Firefox. Any iOS devices are brought in by those of us who own them. This is not a place for "whose is better than whose", rather - this is what is being used, can we please have it added to the testing. Thank you!]]></description>
			<dc:creator>Marilyn Kay Wiley Howard</dc:creator>
			<pubDate>Thu, 11 Oct 2012 14:36:20 --700</pubDate>
			<guid>http://tech.lds.org/blog/531-recommended-browsers-for-ldsorg-tools#comment-1754</guid>
		</item>
	</channel>
</rss>
