If you’re trying to access the site with IE6… well, I guess you know it’s broken. But.. the good news is it’s not as broken as it was, and it’s getting better. Today is the first day I got to test on IE and of course this site isn’t official yet either.
So keep your fingers crossed and lets hope everything works on IE by nightfall. Done at 5:38pm, remaining non-critical items moved to todo list.
What now works – Updated 5:35pm
- navigation, browsing, etc
- clicking edit and viewing source
- saving and deleting via AJAX
- todo lists (IE didn’t like item used as a variable name and doesn’t like grey… it’s gray in Microsoftville)
- This page itself renders wrong (second title at the bottom like the parser isn’t finding the end of the unordered list *sighs*) IE was replacing \n with \r\n after an edit and breaking the parser (TiddlyWiki bug AFAIK, not my doing)
What is still broken
- proper error handling on IE when an unexpected error (server disconnects or connect is lost) occurs because with IE I have no way of knowing which request to tie the error too – but unelss something weird happens saving should work just fine
- style and CSS issues
Seems the IE does not support assigning dynamic attributes to the XMLHTTPRequest object… I assign the title of a tiddler so that if a weird error should happen in the callback I know which tiddler did not save/delete etc… it was working fine in Firefox. I’m really not liking the idea of writing my own queue or something to keep track of these requests.
Any JS experts at there who could help? ContactMe