Okay, this is interesting. It appears that I’ve managed to mung up the code for my pages somewhere so that someone using Internet Explorer 5.2 under Mac OS X cannot leave a comment. Other browsers can, however. I’ll use the comments for this post as a testing ground to try to narrow things down.
Update: Okay, this is an interesting one. All browsers work fine, except Mac OS X 10.2.1/Internet Explorer 5.2.1 (4717) and Mac OS X 10.2.1/OmniWeb 4.1 (v422) — and they’ve got different problems that may or may not be related.
Omniweb’s problem I think is simple enough. Rather than using the … tag to create the ‘Post comment’ and ‘Forget me!’ buttons, I’m using the <button> tag, which OmniWeb might be checking on. That’ll just take a quick tweak of the code to verify.
IE’s problem though, I’m stuck on.
In MT’s default installation, clicking the ‘comment’ link on any post brings up a pop-up window, the code for which is fed from the ‘mt-comments.cgi’ module. When I removed the pop-up, I directed the link to go to the individual post page and scroll down to the comments section. Posting a comment then calls mt-comments.cgi which writes the comment into MT’s database, rebuilds the post page with the new comment added, and redirects back to the post page.
For some reason right now, though, when a comment is posted from IE, the only visible action is that the window refreshes, only it’s being refreshed by mt-comments.cgi (as if mt-comments.cgi is being told to draw the contents of the pop-up window from MT’s default installation), and the new comment that should have been posted disappears.
Grr…I have no clue what is doing this, or how to fix it.