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 Leo,
I was able to use this with a few tweaks to make it work in our solution.
Thanks!
Thank you very much. We will be testing the fix over the next few days and let you know if everything is working as expected. Again, thank you.
We are moving to upgrade to Webgrid 9 in our product. Could you please give an idea as to when the fix will be out for Chrome 43. We have some upset customers that need a response.
We need this fix before chrome 43 is released so that we can no interupt our customers business.
Your prompt response is appreciated.
When you say targeted to WebGrid9, does that mean it's not going to be available for WebGrid8? WebGrid8 is what we need it for. We can't just switch to WebGrid9 without extensive testing.
Again, we need this fix ASAP, we need to do testing, build and deploy to our customers prior to Chrome 43 being released. If this is not going to be the case, we need to do some reevaluating of the situation.
Does WebGrid9 have the same issue that WebGrid8 currently has with Chrome43beta where it simply doesn't work?
So does this mean that you recognize that Chrome 43 is going to break WebGrid?
If so, that means that our customers will more than likely auto updated to Chrome 43 and we will be without a working version of WebGrid until you decide to release the fix. We also need to test, build and deploy which then comes to several weeks. This isn't going to be acceptible. I understand that it isn't your fault that Google is making breaking changes, however you should be on top of this quicker than you have been. It took almost 36 hours for a reply to a ticket that shows that your product is going to break.
This really needs to be looked at. It is probably only a few days till 43 is out of beta which means that 43 could cause major issues for your product. Please give me an update.
Hi Yudi,
There really needs to be a better way to deal with this.
1. This affects various types of cells not just webcombos
2. I don't have a static list of columns. This needs to work for any cell in any grid
Is this something you will consider releasing a patch for?
Hi 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?
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
Creating your account...