I’ve found that even the latest version of Carousel2 (0.1.7 as of this writing) breaks in IE7 and IE8. And although IE7 doesn’t matter much, IE8 does because it is the newest version of IE that will run on Windows XP. Sadly, many people still use XP, so we need to test against IE8.
If you’ve noticed any problems in IE8 when using Carousel2 (in FW5.x or FW6), I would encourage you to offer a report here.
For now, there are only two pages in my test site that use Carousel2, and both exhibit the problem (in IE7 and IE8, but not IE9/IE10 or other browsers):
A big reason to upgrade from Carousel1 is because Carousel2 offers the highly request feature of WRAP. You no longer are zapped back through all your Carousel Panes when you reach the end! It’s great! Give it a try.
Here is the latest Google Analytics data for our website (we’re based in Japan), showing just how huge a percentage of our Japanese web visitors still use IE8:
I thought about going back to Carousel 1, but it doesn’t work at all on my new site layout, despite the fact I’ve not yet moved my document to Freeway 6. I’m still in 5.6.5. Again, here are the two busted pages in my test site:
Sorry it has taken so long to dig this out, the bug was in the setStyle method in Prototype, or maybe my use of it. Version 0.1.9 is posted, and tested at this page: Carousel 2
Walter
On Feb 4, 2013, at 3:03 AM, JDW wrote:
Here is the latest Google Analytics data for our website (we’re based in Japan), showing just how huge a percentage of our Japanese web visitors still use IE8:
I thought about going back to Carousel 1, but it doesn’t work at all on my new site layout, despite the fact I’ve not yet moved my document to Freeway 6. I’m still in 5.6.5. Again, here are the two busted pages in my test site:
Not a problem, Walter. I know you’re very busy right now getting Actions tweaked.
I verified your new Carousel2 Action 0.1.9 fixes the problem in IE8. I verified this on your test page and on the two pages in my own website (which I posted previously in this thread).
IE7 now splatters the Carousel Panes across the browser window (in a worse way than Carousel2 ver.0.1.7 ever did), yielding a “type mismatch” browser error. But IE8 (and higher) is perfect.
I verified all is well in IE9 (Win7) and in IE10 (Win8) too. IE9 on Win7 flashes the pasteboard panes into view for a split second and then they vanish, but I am guessing that is due to the slowness of our IE7 computer. I don’t see it as a big issue. I don’t see that at all in IE10 on Win8.
IE7 now splatters the Carousel Panes across the browser window (in a worse way than Carousel2 ver.0.1.7 ever did), yielding a “type mismatch” browser error. But IE8 (and higher) is perfect.
I’ve finally found a fix for the Carousel2 incompatibility in IE7. As I mentioned before, in IE7 and earlier, and the browser duplicates your main Carousel graphic and throws the duplicate above the original. In my case, that duplicate covers up 1/3 of my navigation bar. And although we can argue that IE7 isn’t work worrying about, I’ve nevertheless found a solution.
Changing the class name of the Carousel DIV using JavaScript is the fix. I simply put the following code into Page HTML Markup, Before :
If your HTML box (DIV) is not named “Carousel” then either change your box’s name to Carousel, or change the code above to match the name you are using.
The end result in IE7 is that your original Carousel graphic will display, but of course no other graphics will roll into view — Carousel will be dead. But that is acceptable to prevent the main graphic from being duplicated and splattering across your web page in IE7 and earlier. And of course your Carousel will work great in IE8 and above, as well as in Firefox, Safari and Chrome.
As time goes on I forget all the hacks I have to come up with to keep my sites from falling apart! But as my previous post states, the following code is the fix for IE7 and below:
Either change your HTML box (DIV) name to “Carousel” in Freeway, or change the word “Carousel” in the code above to match your HTML box name.
Placement is everything. I found the code above does not work if you place it in “Before ” in Page Markup. You must put it in “Before ” for it to work.
Although most of you honestly couldn’t care less about IE7 or below these days, the fact is that it’s just good practice to consider what you can do to keep your website from completely falling to pieces in old browsers. Some things I will ignore, but when a huge graphic gets duplicated and splattered atop the site’s navigation bar, it’s time for me to take action. The above code does just that for Carousel2.
