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
Latest Development Blogs
ForumPostTopic
Browse By Tag
Within our domain we have many different independent web sites. Some of these sites require that the user be in compatibility mode for IE browsers. Most sites, like those using webUI controls require the user NOT to be in compatability mode. So those sites use the <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" /> solution to force the browser to ignore the compatability settings and render the page in the browsers standard mode, works great except for the webGrid. Webgrid appears to ignore this and uses the compatability mode setting of the browser. So for IE10, the columns are misaligned and in IE11 no data is shown at all and get the error: Line: 1 Error: Object doesn't support property or method 'attachEvent'.
I am using 2015 R1 controls. Using <!DOCTYPE html> and renderMode of HTML5.
Is there a solution, other than telling each user not to use compatbaility mode on this site but you need it on that site!
thanks
... So those sites use the <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" /> solution to force the browser to ignore the compatability settings and render the page in the browsers standard mode, works great except for the webGrid. Webgrid appears to ignore this and uses the compatability mode setting of the browser. So for IE10, the columns are misaligned and in IE11 no data is shown at all ...
I tried to reproduce the reported problem by creating a simple page of WebGrid. The page uses html5 doctype declaration: <!DOCTYPE html>. RenderingMode of WebGrid is set to HTML5. The meta tag (in the quoted message) also added into the page.
However, I was unable to replicate the problem. WebGrid is rendered in IE 11 without any issues. I'm using 2015 R1 controls with following details: WebGrid 9.0.7200.4 and WebUI.NET Framework 3.0.5000.916.
Should you find anything that I might miss during my attempt to reproduce the problem, please feel free let me know. If necessary, I can send you my simple page.
Sorry for the delay in sending this.
Yes, my mistake. I forgot to add the test site into the list of Compatibility view WebSites.
I will have this discussed with the team and will get back to you as soon as possible.
When compatibility mode is enabled, the browser is detected as an old browser. WebGrid will use JS file that utilize attachEvent to binds the specified function to an event, so that the function gets called whenever the event fires on the object.
Adding the above meta tag will force the old browser to act as modern browser. It will shows exception telling that object doesn't support property or method 'attachEvent' (due to the fact that addEventListener should be used instead of attachEvent).
WebGrid development team propose a solution for such scenario. They will introduce a property which will force use the JS for modern browser. This enhancement is filed under ASPNET-190.
I will keep this thread updated with any news I heard from the team regarding ASPNET-190.
Hi,
I would like to know if this issue is solved yet.
Hi John and Henrik,
Thanks for your patience. This issue has been moved to a higher priority at the time being. We will keep you informed when the backlog is implemented, estimated in a day or two.
Hello John Bonin and Henrik Ingenäs.
The reported problem under ASPNET-190 has been resolved. The development team has researched a way to be able to detect the compatibility mode automatically, so users don't have to set anything. It just works.
I enclosed the nightly-build of ISNet.WebUI Framework 3.0 as attachment (WebUINET3_0_5000_968.zip).
In order to apply the nightly-build of ISNet.WebUI Framework 3.0 on development PC, you will need to apply the hotfix manually. Please refer to To apply WebUI.NET Framework hotfix section in Apply ASP.NET Product Hotfix Manually tutorial article. If you are using Windows 7 or newer as the operating system of your development PC, you will need to use gacutil to remove/uninstall (gacutil /u [assembly name]) and install (gacutil /i [path to assembly file] assembly into GAC.
Last, please don't forget to apply the nightly-build of of ISNet.WebUI Framework 3.0 on your project/web site.
Please let us know if you have different result.
An initial test shows that the fix works. Still have a more detailed test to verify it...
Please take your time to test the nightly-build. Should the problem persist, please feel free to let us know.
Look forward to hearing back from you.
this build has SOLVED our problem. Thank you. Been tested and all is well.
Glad to hear that the build has resolved the reported problem.
Will this fix (or has it already been) applied to the new 2016 product? Don't want to download and install the new release only to find it doesn't include it.
It will be released as hotfix (available on Update Manager), as well as installer later. We're committed to update installers on monthly basis, in addition to Update Manager.
In our case the patch did not help. We still get column heading that are out of line. See attached file.
Internet Explorer 11.0.9600.18230
Display Intranet sites in Compatibility Mode - Checked
<!DOCTYPE html>
<meta http-equiv="X-UA-Compatible" content="IE=edge"/>
RenderingMode="HTML5"
Thank you for the detail information.
A report has been submitted to WebGrid development team regarding this problem. It is filed under ASPNET-363.
I'll keep this thread updated when a night-build hotfix is ready to be evaluated.
Thanks Yudi
Any update on this issue?
ASPNET-363 is still in progress state. I'll let you know any news I heard from the team regarding ASPNET-363.
Hi Jim,
I'm sorry for the delay in replying. Just checked on ASPNET-363 but it's still in a progress state. I'll inform you once it's fixed.
Regards,Erwin Sanders
Intersoft,When is this going to be fixed? Please give me a date because I need to inform my management. This issue was first reported back in August 2015, and here it is, May 2016, and it's not fixed yet. I'm currently using WebGrid 8.0.7200.260, and WebUI version 3.0.5000.974. (The latest versions currently avaible for download). Please fix this. Jim
In fact, I reported this issue from June 2015. But it still couldn't be fixed until now. Please notify me when it fixed, too.
Could you please test following workaround for ASPNET-363 and let me know the result?
div.WG5-F div table { width: 100%; } .WG5-Header { box-sizing: border-box; }
Add above style to the page which has WebGrid inside. For your information, this workaround works on my simple page running WebGrid 10 (10.0.7200.24) and WebUI.NET Framework 3.0 (3.0.5000.974).
For reference, can check the attached simple sample.
Glad to hear that the CSS fix resolved the reported problem (as workaround for ASPNET-363).
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