Well, it WAS a real IE10 we were testing previously, although it silently upgraded itself so I now need to work out how to downgrade.
Doesn't help though in either cases though - we need this working on IE11 anyway.
So either
Doesn't help though in either cases though - we need this working on IE11 anyway.
So either
a) How do we force it to use IE10 mode (not "Edge" which seems to be the default)
b) Make JavaScript replace function work on IE11?
The second is naturally preferred.
My suspicion is still that regardless of IE10 or 11 somehow its being run in compatibility mode, which if thats IE8 would explain problems with Trim().
The second is naturally preferred.
My suspicion is still that regardless of IE10 or 11 somehow its being run in compatibility mode, which if thats IE8 would explain problems with Trim().
~~~
Thomas & Bertines online review show:
http://randomreviewshow.com/index.html
Try it! You might even feel ambivalent about it :)
Thomas & Bertines online review show:
http://randomreviewshow.com/index.html
Try it! You might even feel ambivalent about it :)
On 4 October 2014 17:32, Steve C <steve@steveclaflin.com> wrote:
You should try to get your hands on a real IE10. My experience with IE11 is that its emulation of earlier versions is far from perfect, particularly with the JS engine. I've had GWT code that failed in IE11 emulating IE10, but worked fine in a real IE10.
On Friday, October 3, 2014 1:49:10 PM UTC-4, darkflame wrote:Ok, it also works if its left as Edge, but the user agent is explicitly set to "Internet Explorer 10"
Whatever Ie10s default user agent is (ie, not touching the settings) does not work, however.
IE is weird.
It looks like my workaround is simple then; force it to use Ie10 mode and not compatibility?
(although Edge would be better for future proofing wouldn't it?)~~~
Thomas & Bertines online review show:
http://randomreviewshow.com/index.html
Try it! You might even feel ambivalent about it :)On 3 October 2014 19:37, Thomas Wrobel <dark...@gmail.com> wrote:ah, ok...hmm.
It crashes in EDGE which is selects by default.It works in 10 if its specifically set to that.It works in 9 (but other stuff is broken, which is expected)
(This was tested using IE's emulation selector)
Could my html markup be making IE select Edge wrongly?
Isn't Edge supposed to be the newest it can manage?~~~
Thomas & Bertines online review show:
http://randomreviewshow.com/index.html
Try it! You might even feel ambivalent about it :)On 3 October 2014 19:28, Jens <jens.ne...@gmail.com> wrote:Could it be that your IE 10 runs in compatibility mode? In that case it might not support JavaScript String.replace().-- J.----
You received this message because you are subscribed to a topic in the Google Groups "Google Web Toolkit" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-web-toolkit/UoWCYwOCaVQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment