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
, 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
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.