If a non-malicious page crashes your browser, then your browser is to blame. The page may also be faulty, but your browser is definitely faulty.
Okay, so you say, that if the wiki is sending bad data to the browser, that the browser does not expect, and the browser crash, its the browsers fault?
Yes.
So if I fill up my diesel car with Petrol 95octan and the engine gets broken forever and the car engine need replacing, then its the car's fault that it didnt accept "bad input"?
If you introduced sulfuric acid into your car engine, then no, I would say you intensionally fubar'd your car. If on the other hand, a normal sample of petrol was introduced to your petrol engine and your engine failed due to that petrol (or normal diesel to a diesel engine), then I would conclude that your engine's fault tolerance was inadequate.
If a browser fails because it is vulnerable to malicious attack (virus), well that's unfortunate and should be immediately fixed. But it is unacceptable to consistently fail during normal operation.
We can and should expect more validation from our browsers than our physical cars. If you tried to open a diesel file with your browser, it should know that it can not handle it and fail gracefully: "I'm sorry, this is an invalid file type". A crashing program is always a faulty program (or system).
I understand that you hate IE, but thats not the topic of this discussion.
I do not hate IE. Microsoft has introduced a huge number of brilliant innovations, but they have fallen behind and have not kept up with standards nor kept their browser robust.
You have three options. Use another browser. Send the report to Microsoft and let them fix it. Or expect the maintainers of the website to try to figure out what particular
normal and valid piece of code is making your unstable application fail.
The maintainers will of course consider this because there may be numerous people who continue to use faulty tools. But I'm suggesting to you to take matters into your own hands.
The topic of this discussion is a serious bug in the wiki that crash the browser.
That
may be true. But the more likely explanation is that a serious bug in the browser is triggered by the innocuous wiki.
Perhaps you could try to deconstruct the web page and figure out what is causing your browser to fail. Microsoft would appreciate it. If your message makes it to the engineers, you would help improve the outdated browser. The wiki maintainers may appreciate it as well, if your environment is not a unique case.
I wish you the best of luck with your chosen tools.