Board Thread:Support Requests - Getting Technical/@comment-1852193-20200313053705/@comment-9605025-20200313064028

Okay. It looks like I spent a little too much time composing my response. I'll paste it below in case any of it is still relevant. With regards to Chrome, I am not having any issues. - Edit:

If it is truly an issue with IE11, you can report it to Fandom. However, the chance they do anything about it is exactly 0%; I 100% guarantee it. - Original Response:

Sophiedp, Special:CreateNewWiki appears to be available only here on CC and on the UCP wiki. The one here just redirects to the one on the UCP Wiki.

Sonic2479, unfortunately a decent number of web developers don't like supporting IE anymore; this includes Fandom. Fandom removed IE from its list of supported browsers some time ago and has refused to fix IE bugs since before that. As a fellow IE user, I am very annoyed at this. However, it seems there is no way to change Fandom's stance on the issue. I assume this issue with creating a new wiki is because you are trying to use IE. 

Most of the new features Fandom has produced over this past year or so do not work with IE. Even ones that appear to have simple fixes have been refused attention. In a comment on one of MisterWoodhouse's blogs, I simply asked if the editor for the UCP was compatible with IE and the answer was "We no longer provide support for IE11, even on the legacy platforms." (see here). Given the number of things that are not IE compatible on the "old" platform, the grim reality is that the UCP will likely be completely broke on it; like how Community Builder wikis were. Below is an in-comprehensive list of things on the "old" platform that don't work in IE. I will indicate whether or not it can be fixed with CSS (i.e. the issue is just display). Most of what cannot be fixed with CSS appears to be fixable with JS ES5-compliant polyfills. But even that is too much extra work apparently. I have placed polyfills for some of the common issues in my personal JS but it does little good. Because global and site JS typically run before personal JS, the polyfills are not in place when they are needed. Seriously guys (web devs), is it that hard to remember to use the match function instead of the includes function? I suppose the biggest issue is new syntactical sugar (short-hand notation) because there is no simple fix for that.
 * 1) Special:Analytics - partial
 * 2) Special:Insights - yes
 * 3) Return to page after login - no
 * 4) Announcements - partial
 * 5) Discussions - no

I had though about adding a script for polyfills to the dev wiki so that at least users posting JS there would have an easy way to make their scripts ES5-compliant; just import the polyfills at the start of their script. However, if the UCP is going to prevent users from using IE all together, then there is no point.