iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Hi,
our current application wide setup is that we force document mode 8, because we expose through 4.0 framwork shell, some old 1.1 framework pages.
And ie8 allowed to modes per pages, standards for new pages and quirks for older ones.
http://screencast.com/t/6LvB6kCrPzs
Hi Bernard,
Do you have any other work arounds? We can't force the user-agent string from code (unless I am mistaken?). This does work if we change it in the dev tools in IE but we can't expect our customers to switch this every time they log into our application.
We use document mode emulateIE8 because the columns don't align properly otherwise. When switching the document mode to IE8, the grid now shows up but the columns do not align properly.
This is incredibly urgent as it affects all of our customers on all versions of our application. Please let us know as soon as possible if you have anything we can use.
Regards,
Ryan
Hi Ryan,
Actually, there are no workaround to change user agent string to Internet Explorer 8. We usually suggest our customer to change its doctype to HTML5 and use our control in RenderingMode HTML5. We are doing this because when Using IE11 and IE10, those Internet Explorer only support HTML5 as its primary doctype. Especially when you're using IE11, there are many obsoleted function that we have handle by using RenderingMode HTML5 and HTML5 doctype. Hope this helps.
Regards,Bernard
So we are using the new hotfixed DLL's for the grid and other controls to render in IE11. For the most part things are running more smoothly, but we are still receiving the HTMLElement javascript errors when using the Meta Tag to emulate IE8. The odd thing is the controls appear to be rendering correctly regardless of this JS error. As I've mentioned before, the IE8 meta tag is still required for style/markup reasons on our older versions as we can't feasibly change every past released version of our application. We are slowly phasing out these older browsers, but are not complete in that task.
Is there anyway you can add feature detection for the HTMLElement object before using it in the IE11Engine you use such that you defend against these JS errors?
Actually this error happen because when you emulate IE, it only change the document mode to IE8. This might cause problem when our API want to get HTMLElement which different for each browser type and browser doctype. As proof, if you change the user agent string to Internet Explorer 8, the javascript error that you're facing won't be appear. When you're using document mode and user agent string to IE8, Internet Explorer rendering method will changed to XHTML which our control expected as IE8. I think there are no other way to pass this issue except by changing your user agent string to Internet Explorer 8 or by changing its doctype and RenderingMode to HTML5. Hope this helps.
Cant you just put that piece of code inside try-catch block?
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname