>>Interesting. I cannot remember, but I looked
>>it up in the css-d archives and it turns out
>Frankly, I get a lot of such mails, and if
>I’d have to answer them all I wouldn’t have
>time for anything else. Besides, at that
>moment I was very busy with writing my JIR
>script and getting quirksmode ready for
Ok, this is more than understandable.
>>Some time passed, as ALA, same as evolt.org
>>takes some time to publish.
>>No word there, no word of PPK on the list
>>that he published a version on
>Now this is untrue. On the same day you wrote your mail to me,
>I announced quirksmode.org on css-d and I explicitly said
>that it contained a JIR script.
>So you could have known.
The same way you could have taken my email about it more serious.
It is OK for you to not answer the immediate answer-mail to your mail but I should find the mentioning of JIR in the last sentence of the announce email of quirksmode.org. I get a lot of mails, too.
The “interesting discussion” you mentioned could and should have happened in the first email then, it would have prevented this article and my script (which is not as bad as you make it depending on how you use it. Granted, certain elements are bad).
In your article you mention the overuse of
loops. I agree with the break statement idea and will insert it.
However I don’t consider invalid XHTML better.
It’s a matter of what you do, my example works with pages that get generated with random names and IDs (ASP.NET likes doing that), yours assumes I can totally control the HTML, and add an extra attribute that results in invalid xHTML.
Also, let’s not forget that image replacement of headers is a cosmetic change, it is unnatural for a header to be an image. Hence you should stick to replacing headers for an article only. Your example of 20 headlines in one document would be either a whole book or an extreme overuse of headlines. This is were image replacement fails, the overuse of it (latest CSSZENGARDEN entries prove that).
As for the alt text displaying, if you read the first comment, this is a known mozilla bug.
I totally agree with your bit about assumptions, and will test some of my stuff as soon as my screen reader arrives.
It is a shame that there is no free screen reader on WIN, and that the prices are that high.
I was enthusiastic about the idea, and released something too fast. Agreed. However you could have emailed me with your concerns and I would have made damn well sure that these changes get implemented here, rather than pointing the finger and publishing your article. I cannot undo what happened.
There were crappy ALA articles in the past, and every cutting edge idea / article has it’s drawbacks. FIR was the best till Joe Clark proved us wrong.
As stated in the article I am willing to constantly update the script, and I see it as an example for other developers to come up with own solutions. The style switcher script here got improved this way aswell.