On a photo page, when "Play Slideshow" is initially clicked, the slideshow opens correctly. When the slideshow window is closed, and "Play Slideshow" is clicked again (or "Play Slideshow" is clicked on any other photo page), the slideshow almost always opens with small images. This happens in Safari 5.1.5, but not in FireFox. If Safari's cache is cleared, the slideshow agains opens normally, but again, usually only once.

For example, go here: http://www.frisons.org/Carrolls_Photos/ ... Trail.html

Has anyone else seen this?

Carroll

Hi Carroll,

do you have access to multiple Mac Computers and experience the same issue on all of them?

Reason I ask is that I don't experience the issue you describe on my MacBook Pro 15" and see no difference in the size of the pictures between Safari and Firefox nor Safari itself or Firefox itself even after closing and reloading and reopening multiple times.

Whereas on my MacBook Air 11" Firefox displays images which are slightly smaller than in Safari but again they are constantly the same size after closing, reopening, reloading, ... on both browsers. So I don't experience the problem on this Mac either.

Regards,
Cédric

Hi Cédric,

The problem is found on both of our computers, in these accounts on both:

Our Standard user account
Admin
new Standard account to test this issue

Computers:

iMac
20-inch, Early 2009
2.66 GHz Core 2 Duo

MacBook Pro
17-inch, Early 2008
2.5 GHz Core 2 Duo

Carroll

Since for some strange reason it now happened to me as well...

Have you tried going to Inspector, Photos, Slideshow and selecting Full screen?
Maybe it doesn't happen with full screen enabled...

Let me know,
Cédric

Cédric,

No, unfortunately, that does not seem to make a difference. I changed "Forest Trail" only.

Do you see a difference?

Carroll

I have no clue, sorry. It works for me with no problems in 95% of the cases, but I have no clue why it doesn't work in those other 5%.
Let's hope Apple fixes Safari?

I would stick with full screen anyway...

OK, thanks for taking a look. At least I know It's not just me.... Hee, hee.... I'm not sure when this began as I haven't posted anything or even gone there for about a year. Now moving the site to HostExcellence, fixing galleries, adding pages, etc. Looking forward to trying some stuff in your ebook.

Regards,

Carroll

Dear Carroll and Cedric,

I have had exactly the same problem with slideshows on my two sites, now with HostExcellence (see for example http://briangrassom.com/Painting.html and other photo pages on that site). This only began recently, so I'm not sure if it is coincidental with upgrading to Lion 10.7.4, or moving from the MobileMe server to HostExcellence.

But I have checked in the 'sites' folder opening the 'index.html' file on my Mac from which the websites are uploaded via Cyberduck to HostExcellence, and the problem is there as well: so, it looks like it may be something to do with iWeb (I have version 3.0.4) and/or Lion? - particularly if Carroll has the same problem and has not yet moved to HE.

The slides will display full screen (in which they are set in iWeb's 'Inspector') immediately upon opening the slideshow, but invariably they will display much smaller (too small) if the show is re-opened in the same session, or if I move to another page's slideshow. It does not matter if the slideshow is on the 'photo' page, or in an embedded 'album' page. In any one session the slide size in all pages will be erratic and unpredictable. The same thing happens if I view the website on our iPad.

I wonder if more people are experiencing this issue just now, and if it therefore has something to do with upgrading the OS system to cope with the current emergence of iCloud and demise of MobileMe: or if it is something technical, limited to a few users and their particular website designs?

Thanks for reading this rather long missive.

Bri.

A post-script to the above. I have now tried opening the website with 'Firefox', and the slideshows display as they should. So the problem would appear to be an issue with Safari (I have 5.1.7). Does anyone know how this might be addressed?

Thanks,

Bri

Still hoping Apple fixes Safari...