PDA

View Full Version : Windows 8/IE 9/Forum <Enter> key Problem



Mark Powers
17-Jan-2013, 10:35 AM
For any of you trying out windows 8 with Internet Explorer 10, I have had a problem when using that combination with the DAW forum and using the <Enter> key. The enter key did not work at all in the forums. I tried Chrome and it works fine.

Hope this helps someone else.
Mark

Mike Cooper
17-Jan-2013, 10:44 AM
In IE10, you need to go into the Developer Tools and you can set the "Compatibility Mode" with IE. Sounds strange but true.

Mike

Mark Powers
17-Jan-2013, 11:01 AM
Mike:
Thanks, that seemed to do the trick.
Mark

Richard Hogg
17-Jan-2013, 07:13 PM
Isn't "Strange but true" the Microsoft motto :)

Mark Powers
18-Jan-2013, 10:03 AM
Yes I think it is Richard!

chuckatkinson
24-Jun-2013, 09:00 AM
I think this setting is transient - you will have to reset it each time you open IE10.

Harm Wibier
25-Jun-2013, 03:19 AM
You can go to tools (hold alt to show the menu) and then compatibility view settings. There you can add sites to a list which will make them show in compatibility mode all the time. Or download Chrome or FireFox ;)

Harm Wibier
25-Jun-2013, 03:41 AM
You can go to tools (hold alt to show the menu) and then compatibility view settings. There you can add sites to a list which will make them show in compatibility mode all the time. Or download Chrome or FireFox ;)

Note that this seems to be working per domain. So doing this switches back all dataaccess.com sites including for example http://demo.dataaccess.com/VDF_DynamicAI/index.html that doesn't work in compatibility mode at all.

Peter van Mil
25-Jun-2013, 04:04 AM
Harm,

Therefor I have asked for the compatibility setting of the forum. (Dennis and Stephen are looking for this).

See: http://support.dataaccess.com/Forums/showthread.php?50660-Compatibility-IE10

JimNC9
26-Jun-2013, 09:02 AM
FWIW, I have the same problem here, but I don't have the problem on another site with Version 4.1.10 of vBulletin.

Dennis Piccioni
26-Jun-2013, 10:33 AM
Odd, perhaps they have implemented some workaround, since vBulletin has acknowledged some issue with this addressed in newer versions.