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 there,
We are and having been using the Intersoft controls for some time and recently ran into an issue with IE 11 in regards to Grid Rendering. For a while, the grids were rendering fine in all of our supported versions, 8 through 11. On February 11, 2014, Microsoft pushed some security hotfixes out and the WebGrid stopped rendering in IE 11, when previously it was working fine. The security bulleting with the list of patches that can cause this issue is:
http://technet.microsoft.com/en-us/security/bulletin/ms14-009
If the Web Server has any of these security patches, the grids will stop rendering with no changes to the application. Uninstalling the security patches will allow the grid to render again, but this is not a good solution. For example, installing the 4.5.1 .Net service pack will also cause the same behaviour and it cannot be easily removed from a server. We also don't like the idea of not applying security patches to our servers.
We currently do use the DocType in our production versions of our application:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
As well as the meta tag:
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
These are currently mandatory for our IE 8/9/10/11 support in the versions that are in production. We'd like to know if it would be possible to:
a) Receive a document or be provided a link to a compiled list of release notes/changes/hotfixes for the WebGrid such that we can compare to our production versions and determine a risk assessment of dropping in the new DLL that may or may not be compatible with the older code with little to no re-work.
b) Is it possible to recieve hotfix patches to the DLL versions of the grid that we use in those older versions of our application where the only fix to them is the change that allows the IE 11 render fix that you put in the most recent version. (258 I think)
c) Are you aware of the security issue and have a workaround to force our servers to see IE11 as IE10 or 9?
Essentially we want to find a solution to the IE11 rendering issue, not only for our future versions that will use HTML5 Doctype and the newest WebGrid releases, but also allows us to fix some of our older versions of our product that requires older DocTypes without imposing too much risk and a full regression testing requirement.
Thank you,
Questica
Hi,
We are aware with this issue in IE11 and IE10 so we usually ask user to change its doctype to HTML5 doctype. This is necessary because IE10 and IE11 has drop its rendering method for HTML4 and XHTML. Right now, IE10 and IE11 using HTML5 doctype as its standard rendering.
Perhaps, you should consider the usage of those meta tag. The meta tag above only force to change its document mode to IE8 but it's not changing its user agent string. When you're using this tag, our framework will render our control regarding its rendering method but in its progress there are many wrong validation. This is because some of our API needs to validate browser so our control run properly in many browser.
I will ask our developer team regarding this issue for XHTML and HTML4 doctype in modern browser. But perhaps, you should change your doctype to HTML5 so you web page will rendered properly in IE11 and IE10. Or you should validate the browser in in your project so it will change the master page to HTML5 doctype for modern browser and it still using XHTML doctype for old browser (for example: IE8, because IE8 doesn't support HTML5 doctype). You should also change RenderingMode property in our control so it will rendered properly in specific browser. This might not causing any problem in the future because our developer will consider any bug or feature request in HTML5 doctype for modern browser. Hope this helps.
Regards,Bernard
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