Marcus Spieka
Top achievements
Rank 1
Rank 1
Marcus Spieka
asked on 19 Jan 2015, 10:58 AM
Hi,
I am not sure there have been threads about this issue before. I could not find anything quickly. I am planning to use Telerik hosted within a standard COTS application by means of an IFrame. I have limited possibilities to change the standard application (because, well it is a bad practice for a COTS application). The browser is IE9 which is a company standard and I am not able to change that too. The problem is that the standard host application forces the browser in Quirks mode and if I change that to standard (strict) mode (e.g. by means of an http header setting X-UA-Compatible to IE=edge) other things breaks for obvious reasons (IFrame height set to "100%" now interpreted as 100 pixels, font resizing issue probably caused by the box model interpretation, etc.).
What is my best option to have Telerik controls working correctly in this scenario? Some things just don't seem to work for no obvious reason even in IE9 strict mode, such as selecting an item from a dropdown list in a custom popup editor in a grid using the MVC Html.DropDownListFor. For example, I can click on an item in the drop-down list but it does not get selected. There might be other issues I might ran into. To get a feeling about whether I will be able to make this scenario work at all I would like to have some advice from Telerik support and others from this forum.
To summarize I have these questions:
1. What are my chances to make the Telerik controls (UI forASP.NET MVC) work together with the standard MVC controls in this scenario?
2. What are some features I should avoid or issues I should be aware of? Are there any workarounds for them?
3. Except from some styling and sizing issues the standard host application seem to work fine. I might be able to fix things there but some references on how to fix things would be great (I am already exploring stackoverflow, quirtksmode.org, MDN, w3fools, etc.). I guess I am looking for something like a cookbook on migrating from quirks to strict mode. Any good pointers would be greatly appreciated.
Thanks in advance for any help.
Marc
I am not sure there have been threads about this issue before. I could not find anything quickly. I am planning to use Telerik hosted within a standard COTS application by means of an IFrame. I have limited possibilities to change the standard application (because, well it is a bad practice for a COTS application). The browser is IE9 which is a company standard and I am not able to change that too. The problem is that the standard host application forces the browser in Quirks mode and if I change that to standard (strict) mode (e.g. by means of an http header setting X-UA-Compatible to IE=edge) other things breaks for obvious reasons (IFrame height set to "100%" now interpreted as 100 pixels, font resizing issue probably caused by the box model interpretation, etc.).
What is my best option to have Telerik controls working correctly in this scenario? Some things just don't seem to work for no obvious reason even in IE9 strict mode, such as selecting an item from a dropdown list in a custom popup editor in a grid using the MVC Html.DropDownListFor. For example, I can click on an item in the drop-down list but it does not get selected. There might be other issues I might ran into. To get a feeling about whether I will be able to make this scenario work at all I would like to have some advice from Telerik support and others from this forum.
To summarize I have these questions:
1. What are my chances to make the Telerik controls (UI forASP.NET MVC) work together with the standard MVC controls in this scenario?
2. What are some features I should avoid or issues I should be aware of? Are there any workarounds for them?
3. Except from some styling and sizing issues the standard host application seem to work fine. I might be able to fix things there but some references on how to fix things would be great (I am already exploring stackoverflow, quirtksmode.org, MDN, w3fools, etc.). I guess I am looking for something like a cookbook on migrating from quirks to strict mode. Any good pointers would be greatly appreciated.
Thanks in advance for any help.
Marc
2 Answers, 1 is accepted
0
Hi Marc,
I have to admint that the "w3fools" part was really entertaining, although not quite politically correct :)
Now to the discussed topic. Quirks mode is a rather obsolete and unreliable environment for web applications, which should be buried deeply in the dawn of web development. I am afraid we do not support it. Eventhough the widgets may seem to (partially) work at first glance, various problems are to be expected, including broken layout, which cannot be easily fixed. My strong recommendation is to avoid quirks mode at all costs (not only with regard to Kendo UI, but in general). For example, jQuery doesn't support quirks mode either.
Furthermore, there are also complications when using iframes and parent pages in different mode, as IE9+ will unify the two modes.
Assuming that the jQuery version is compatible with the Kendo UI version, and there are no Javascript errors, all observed problems can be safely attributed to the quirks mode, unless proven otherwise, which is unlikely.
1. Using UI for ASP.NET MVC together with standard MVC controls
You should have no problems with that.
2. Quirks mode issues and possible workarounds
We personally don't have such a documentation, as working with quirks mode is practically out of the question.
3. Quirks mode vs Standards mode
http://www.quirksmode.org/css/quirksmode.html
Regards,
Dimo
Telerik
I have to admint that the "w3fools" part was really entertaining, although not quite politically correct :)
Now to the discussed topic. Quirks mode is a rather obsolete and unreliable environment for web applications, which should be buried deeply in the dawn of web development. I am afraid we do not support it. Eventhough the widgets may seem to (partially) work at first glance, various problems are to be expected, including broken layout, which cannot be easily fixed. My strong recommendation is to avoid quirks mode at all costs (not only with regard to Kendo UI, but in general). For example, jQuery doesn't support quirks mode either.
Furthermore, there are also complications when using iframes and parent pages in different mode, as IE9+ will unify the two modes.
Assuming that the jQuery version is compatible with the Kendo UI version, and there are no Javascript errors, all observed problems can be safely attributed to the quirks mode, unless proven otherwise, which is unlikely.
1. Using UI for ASP.NET MVC together with standard MVC controls
You should have no problems with that.
2. Quirks mode issues and possible workarounds
We personally don't have such a documentation, as working with quirks mode is practically out of the question.
3. Quirks mode vs Standards mode
http://www.quirksmode.org/css/quirksmode.html
Regards,
Dimo
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
0
Marcus Spieka
Top achievements
Rank 1
Rank 1
answered on 20 Jan 2015, 05:39 PM
Hi Dimo, actually w3fools is a legitimate site (www.w3fools.com) and their goal is to address the real world complex web issues.
Your answer is really helpful and what it means for me is trying to get rid of quirks mode. However this is a standard ASP.NET 2 web application in which I have to host my application in an iframe. I am looking for "safe" CSS fixes and the like that will fix some minor layout issues in the host application. I have already investigated sites such as the one you mentioned, but I am not sure how much work to expect or where to start. Probably I just have to begin solving issues one by one and see how it goes.
Thanks for your clarifications so far.
Regards, Marc