A lack of new content isn’t the only thing wrong with this blog. In recent weeks, it has also been brought to my attention that the template I’m using is flawed. It looks fine in Internet Explorer (IE), but lousy in any other browser. Users of both Mozilla Firefox and the Mac-based Safari have reported seeing exactly the same formatting glitches. The problem seems to be with the Cascading Style Sheets (CSS) used by the template; IE interprets the CSS code incorrectly, but the person who created the template evidently was using IE to view the result, and concluded that it worked properly.
I’m not proficient with CSS, but my son Ben is, thanks to the HTML classes he took at school. He did some tinkering with the CSS code, but was unable to find a way to make it look right in both IE and non-IE browsers. My friend Virgil came up with a compromise that he says looks OK in both sorts of browsers, and I may end up using it. But there’s one other thing I want to try first. In the course of researching the problem, I stumbled across this trick for putting two versions of the CSS code in external files — one of which is used only by IE, and the other only by other browsers. If it works, this solution will be the best of both worlds. I hope to have it implemented in the next day or two.
UPDATE: The trick I mentioned above did not solve the problem — it doesn’t work with newer non-IE browsers like Firefox. But Ben wasn’t willing to give up. The problem is now fixed, thanks to his supreme excellence as a Javascript hacker. (I was going to say “his l33t h4x0r sk1llz,” but I thought that might be confusing to readers who aren’t fluent in Leetspeak.)