<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Web Site Problem Solved&#8230;.</title>
	<atom:link href="http://www.sandallpark.org.uk/2010/02/web-site-problem-solved/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sandallpark.org.uk/2010/02/web-site-problem-solved/</link>
	<description>Making the park better for everyone</description>
	<lastBuildDate>Thu, 09 Feb 2012 17:48:08 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Don@fosp</title>
		<link>http://www.sandallpark.org.uk/2010/02/web-site-problem-solved/comment-page-1/#comment-680</link>
		<dc:creator>Don@fosp</dc:creator>
		<pubDate>Fri, 19 Feb 2010 13:52:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.sandallpark.org.uk/?p=4725#comment-680</guid>
		<description>Thanks for that - our webmaster is away at the moment but will look at it when he returns.</description>
		<content:encoded><![CDATA[<p>Thanks for that &#8211; our webmaster is away at the moment but will look at it when he returns.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web Help Desk</title>
		<link>http://www.sandallpark.org.uk/2010/02/web-site-problem-solved/comment-page-1/#comment-678</link>
		<dc:creator>Web Help Desk</dc:creator>
		<pubDate>Thu, 18 Feb 2010 02:47:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.sandallpark.org.uk/?p=4725#comment-678</guid>
		<description>Hi

Re your problem with Chrome, this has occurred with a few website galleries and generally relates to image onload properties. On your set up you will need to make adjustments to the file:

wp-content/plugins/nextgen-gallery/shutter/shutter-reloaded.js?ver=1.3.0

Go to approximately line 150 which starts “D.innerHTML” 

Remove the src attribute from the img element.

Straight after the same D.innerHTML statement, type:

document.getElementById(“shTopImg”).src = shutterLinks[ln].link;

So that line will then look something like

D.innerHTML = ”+shutterLinks[ln].title+”;
shutterReloaded.showImg();

Can&#039;t confirm the spacing is perfect, especially with this posting box but with a few trials you should get this to work. The issue appeared to be fixed in a later version of Chrome but just tested on the up to date dev version and back again, so worth the time fiddling around.

Another option but one involving a lot of work would be to change over to a CSS/XHTML gallery. May improve accessibility for some users and search engines plus avoid future browser issues, particularly with one or two burgeoning mobile devices. If you were interested there are many options via search, you might start with searching for Stu Nichols site.

Just a thought and in no way meant to be a criticism of your website. Enjoyed visiting and the images look good either way.</description>
		<content:encoded><![CDATA[<p>Hi</p>
<p>Re your problem with Chrome, this has occurred with a few website galleries and generally relates to image onload properties. On your set up you will need to make adjustments to the file:</p>
<p>wp-content/plugins/nextgen-gallery/shutter/shutter-reloaded.js?ver=1.3.0</p>
<p>Go to approximately line 150 which starts “D.innerHTML” </p>
<p>Remove the src attribute from the img element.</p>
<p>Straight after the same D.innerHTML statement, type:</p>
<p>document.getElementById(“shTopImg”).src = shutterLinks[ln].link;</p>
<p>So that line will then look something like</p>
<p>D.innerHTML = ”+shutterLinks[ln].title+”;<br />
shutterReloaded.showImg();</p>
<p>Can&#8217;t confirm the spacing is perfect, especially with this posting box but with a few trials you should get this to work. The issue appeared to be fixed in a later version of Chrome but just tested on the up to date dev version and back again, so worth the time fiddling around.</p>
<p>Another option but one involving a lot of work would be to change over to a CSS/XHTML gallery. May improve accessibility for some users and search engines plus avoid future browser issues, particularly with one or two burgeoning mobile devices. If you were interested there are many options via search, you might start with searching for Stu Nichols site.</p>
<p>Just a thought and in no way meant to be a criticism of your website. Enjoyed visiting and the images look good either way.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

