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 Karl,
Hi John,
Sorry for our late responses. I think when you're using MultiView control, it will do FullPostback on your page. In first Postback the value will still remain because it still persist our WebTextEditor object in your server side then it will reinitialize our WebTextEditor. After initialize our WebTextEditor will clear its value so it won't have value on second Postback. Perhaps to achieve this scenario, you could save this value on first postback in variable in server side. Then you could set the value in WebTextEditor when PostBack. Hope this helps.
Regards,Bernard
Hi,
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.
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.
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.
Hi Durga,
I couldn't replicate this issue in our local end. Regarding to this problem, I have made you a simple sample. Could you please look at my sample and please let me know if this issue still persist in my sample in your local end? You can download my sample in this link. Hope this helps.
Actually, I couldn't see the error in you attached file. Could you send me your image to my email in rar / zip format? This is my email bernard@intersoftpt.com. Look forward to hear any feedback from you.
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