Wedge

I can do it; IE 10.0.6

Never had any problems either, on Win7 + IE10 at least...

Some older versions of IE have trouble, though, when hitting Enter instead of the Submit button. Not that I could care less about these, though... I know how to fix that, but I d-o-n-o-t-c-a-r-e.

Had a look at the error log... Looks like, your IE10 is failing to transmit the current context to Wedge.
Can you check your JavaScript error log...? (Developer tools.)

Will have to be tomorrow away from pc sadly good that it is just my system didn't trouble shoot before posting I should have!

Nah, it's bad that it's just your problem, otherwise, it'd already be fixed... ;)

Yeah its something with javascript and this system. Sorry for the false report.

What error then..?

Just some syntax errors
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 13166
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 13376
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 9363
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 9363
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737
SCRIPT5022: Caught exception occurred : SyntaxError
jquery.min.js, line 4 character 14737

Well, so that would be a jQuery problem...
Only, it shouldn't happen either way. 4:13166 is e.querySelectorAll(), which is a perfectly valid DOM method, so... Whatever?!

Maybe this could be solved by using $.get instead of $.post on some areas, as it seems related to an 'unfixable' bug in IE10+jQuery that was reported over there. I'm not exactly sure, though... Are you ready to test even more when I apply the change..? :P

Sure I can, thoug ph I might be available at different hours so it might take awhile to reply.

'kay, just reload your homepage, should be updated now...
Tell me if it's still giving you errors, or not!

Uh, what specified prefix..?!
Even then... Wedge is returning HTML, not XML... That's totally crazy.
Remind me

'Like', not surprised you can't, since it's still doing a Post, rather than a Get.
Can you push Like in Desktop mode, Metro mode, and Private mode, just to be sure..?

So, yeah, basically, this is the problem I saw mentioned elsewhere, and moving to $.get fixed it, but I certainly don't like the idea of expecting all variables to be put into the URL in plain sight, but... Whatever...

Pete, what do you think..? $.get or $.post?

One thing at a time. querySelectorAll is a valid method but IE doesn't behave properly with it, as per http://stackoverflow.com/questions/15145108/running-jquery-crashing-on-ie10-win7

The other errors, I have no idea what they are... but I don't see why $.get and $.post should behave fundamentally differently.