Major disruptions caused by Safari

Question

I installed Safari as the default browser. It hijacked the XML file type association, previously associated to Internet Explorer. It is a change that cannot be undone because Internet Explorer fixes only protocol associations, not file associations. There are numerous problems with this:
1. The default style sheet is empty CSS; it does not do anything useful (as compared to Internet Explorer).
2. External subsets in DTD are not read; the pages that used to work do not work any more. The workaround to explicitly declare all entities used by the page is cumbersome and hard to do automatically.
3. When I send a local page to Internet Explorer because I cannot read it in Safari, Safari converts the local path to a file URL performing UTF-8 and URLEncode as intermediate conversions. Internet Explorer is unable to open such URLs except in very special cases where the encoding is transparent.
4. The spell checker in Safari does not handle Polish even though the user interface is in Polish; I understand that Internet Explorer does not include any spell checker whatsoever so the spell checker should be turned off by default.
5. XML transformations that previously worked break, e.g. on msxml:node-set. And it hard to tell where exactly they break without modifying the style sheet.
6. Safari hijacks XML file type but leaves XSL file type alone; this allows an ugly workaround of saving all XML files as XSL.
7. The icons for Safari associations are uninformative (XML) or not present at all (HTM).
I understand the best thing in this situation would be to show Safari the door; however, Apple Software Update will still recommend installing it. With so many bugs and problems, please do not show Safari in ASU unless it is already installed.

Answer 1

I installed Safari as the default browser. It hijacked the XML file type association, previously associated to Internet Explorer. It is a change that cannot be undone because Internet Explorer fixes only protocol associations, not file associations. There are numerous problems with this:
1. The default style sheet is empty CSS; it does not do anything useful (as compared to Internet Explorer).
2. External subsets in DTD are not read; the pages that used to work do not work any more. The workaround to explicitly declare all entities used by the page is cumbersome and hard to do automatically.
3. When I send a local page to Internet Explorer because I cannot read it in Safari, Safari converts the local path to a file URL performing UTF-8 and URLEncode as intermediate conversions. Internet Explorer is unable to open such URLs except in very special cases where the encoding is transparent.
4. The spell checker in Safari does not handle Polish even though the user interface is in Polish; I understand that Internet Explorer does not include any spell checker whatsoever so the spell checker should be turned off by default.
5. XML transformations that previously worked break, e.g. on msxml:node-set. And it hard to tell where exactly they break without modifying the style sheet.
6. Safari hijacks XML file type but leaves XSL file type alone; this allows an ugly workaround of saving all XML files as XSL.
7. The icons for Safari associations are uninformative (XML) or not present at all (HTM).
I understand the best thing in this situation would be to show Safari the door; however, Apple Software Update will still recommend installing it. With so many bugs and problems, please do not show Safari in ASU unless it is already installed.