Mark Wubben, the guy who reinvented :hover as .hover and :target as .target releases, together with Mike Davidson, the second version of sIFR.
I was planning to use it today as an ode to Macromedia, but other things kept me a little more busy and Mark went offline a little early as well. At least, earlier than I had planned him to go offline ;-)
Testing URI generation of comments. Please ignore.
Well if you are generating test comments then I can be off-topic. ;-) I was wondering when you switched from XHTML to HTML? And how do you validate comments now? Incorrectly I presume!
I will post about that later. Comments still have to be XHTML though. I need everything as XML in the backend to remain compatible with existing web tools. Everything that no longer runs on XHTML is made by me. The other parts are still WordPress. The past couple of days I have been moving stuff around for a bit.
Yeah. That sums up why I have not switched myself yet. XML serialisation does have its uses...
First, sIFR 2.0 exists for a few months now (see RC4, for example), CMIIW.
Second, sIFR uses embed elements and sifr attributes. I at least question to use sIFR. Use SIIR instead.
I couldn’t care less about EMBED here. Every device which doesn’t support that element is incompatible with the web. (Therefore HTML5 will most likely include it, but that’s another story.)
And about the version number. I meant the final release in my post, I thought that was obvious. Especially as I have mentioned it before.
Excuse me, Anne.
Sorry, didn't know you needed me, Anne. Thanks for the kind words.
SIIR isn't bad, but it's not really scalable, is it. I mean, I if I resize the text on my page, then the images used as substitute titles don't scale at all never mind in tune. What's the point in that?! Of course, the images can't resize, and so therein lies the problem with it - the end user can't dictate the size of all the text on their pages.
jbot, resize your page and then reload your page and your SIFR text will be in the new size.
[...] the end user can't dictate the size of all the text on their pages.
Common problem with almost all IR techniques. You can partly address this with a larger font size.
[...] resize your page and then reload your page and your SIFR text will be in the new size.
The crux is that the user needs to know this. It breaks the usual scaling mechanism.
You could include something in the sIFR code to display a message on that occasion, along the lines of Please press refresh to adjust the size of the elements which haven't resized with the rest
, or couldn't you? I'm not sure, it would probably be different per browser, if possible at all, now I think about it.
More disturbing in my opinion, you can't select the text on the page in one piece, you have the text in the (multiple) Flash sIFR things and the normal text on the page. One has to disable Flash to be able to nicely copy everything. It's just a three button action for me (shift+p to disable plugins, 5 to reload the page, do the thing and shift+p to enable plugins again), but that's far less intuitive than the refreshing which isn't that far from the lines of expectation.
Frenzie: Ummmm, or you could just hit Select All to select all the text. Or you could drag select as normal. Everything copies just fine. The visual selection feedback is the only weird part.
jbot, resize your page and then reload your page and your SIFR text will be in the new size.
That didn't even come close to working in Win FF 1.0.3. Really, if it's properly accessible, the text should resize on the fly, not via reloading the page.
Joe Clark, I was talking about SIIR, by the way; not sIFR!