Have narrowed it down to a javascript file, which had only the following function in it:
javascript code:
function elem(ent){return document.getElementById(ent);}
And including that function as a regular script still causes the error.
Renaming the function works, except then I get the regular object expected when trying to use the function later. Renaming the function calls results in the same problem.
It's a function I've used thousands of times before, and it works fine before submitting the page, so I'm even more confused then I was before. :/
Hmmm, just manually replaced all the function calls with the whole document.getElementById thing and I /still/ get the error! :@
I'd guess (though my knowledge of such things approximates to zero) that there's something about your javascript that IE doesn't like, and it's eventually dying on the elem() calls, even if it's not that function that's the problem. Can you replace all your JS with skeleton functions which just return dummy values, see if that works, and then build it up from there? Try adding one function at a time, to narrow down where the bug is hiding?
Yeah, was just about to do something similar to that.
If I access my machine over the network I get errors about nulls instead of that message, but it doesn't help if I comment out the line reported with the null error, so obviously there's something earlier that's causing it.
Eliminated the bug with nulls, and it works perfectly fine across the network now. Try it back on localhost, and it's doing the same damned thing. So I track it down and find precisely where the problem is, except I can't find what the problem is. I know it's with an AJAX call, and by using dummy calls and stuff, I can prove everything works individually. Put it all together and I get the bloody 'Operation aborted' again. :'(
