Time to go and play and see how it works.

Example (Only in Safari)

By the way, the permalink to this entry won’t open in Internet Explorer 6 on this machine (XP SP2), though its fine in Firefox. Instead I get the File Download dialog. Other permalinks open fine.

On whitespace I see the headers no problem.

On both your blog and design by fire I get blankness where the replacements should be.

On your latest test page and my own feeble attempt, the status bar never gets to the end and reports that there are “x items remaining” where x is the number of replacements on the page.

I’m convinced it’s something I’m doing but I’m not sure what.

We are aware of this problem and a workaround has been in the sIFR code for quite some time now. We’re going to need a bit more information from you to see if we can replicate your specific problem. (And, perhaps, some more bug reports.)

Also it should be noted that Design by Fire is still using an old version of sIFR (or perhaps even IFR?).

Sunshine-

I don’t believe Paul is using sIFR on Whitespace. It sounds to me like you’re actually have the problem all the time. Do you have problems with other Flash content?

Meanwhile Mark goes on checking if some Mozilla bugs have already been squashed….

Ben

(Editor’s Note: Oops. We just fixed that. Re-uploaded a new RC2 at 12:55pm Pacific Time today, Monday, December 6th. Thanks for the alert and sorry for the oversight.)

Second, the new script conflicted with some js generated layers, with the sIFR replaced content forced to the top (above layers generated by Aaron B’s ypSlideoutMenu). I can’t show you an example, but I narrowed down the difference between RC1 and RC2 that caused it.

On line 333, RC2 says “transparent” : “”;. In what I believe to be the equivalent code from RC1, line 265, it said “transparent” : “opaque”;. I don’t know what I’ve potentially broken by adding “opaque” back into the RC2 script, but at least the layers are now stacking correctly in Win IE 6 and Firefox 1. So, I’m happy for the moment, but I don’t know if that may cause bigger problems for others.

Lastly, RC1 (and previous versions, I believe) incorrectly stacked layers only in Win Opera 7.54, but RC2 doesn’t replace the headline content at all (with either original RC2 sIFR.js or my edited version). Again, not so much an issue in my eyes, but it could be a sign of bigger problems for others.

Thanks again to Mike, Mark, and everyone else!
-ed

(Editor’s Note: We actually decided to change the way window modes were handled in this release. Before, “opaque” was the default. Now, “” is the default. “” is a better default because it takes up less processor power if you don’t need stacking. If you do need to stack DHTML elements though, “opaque” is still supported. We added the ability to pass this in as the last parameter of the function. See the readme file for details. Please also make sure you have the lastest RC2, which was uploaded at 12:55pm Pacific Time today, Monday December 6th.)

Some of my main woes with RC1 was related to the way links were handled. Nearly all of those problems were caused by Macromedia, not sIFR. However, one specific issue was that Firefox on Windows had trouble with links. More specifically, if a page was scrolled, it would require a double-click on a link, as if to first “activate” it, and then follow the link. It is a pleasure that this bug has been fixed in RC2, whether you were conscious about it or not.

As an added benefit of the above bugfix, I’m now using a hover color, and related to that I’d like to add to a wishlist for the final release that you plainly use textfields for links and hovercolors, and not have them reside inside a button, or movieclip as seems to be the case now. The benefit of this would be that links can be right-clicked / copied. While this’ll be a hassle to program, I’m fairly sure it can be done, and I honestly think the – albeit small – usability improvement would be worth it.

We’re running the latest tests now, Mike will make an announcement in the post itself when we’re done. RC 2.1 ;-)