How come to mobile documentation has switched to using "<div data-role="view">
<a href="#my-modal" data-rel="modalview" data-role="button">Open Modal</a>
</div>
<div data-role="modalview" id="my-modal" style="width: 200px; height: 200px;">
Hello!
</div>
<script>
new kendo.mobile.Application();
</script>" as the new format for initializing widgets whereas the web documentation only uses "<select id="multiselect" multiple="multiple">
<option>Item1</option>
<option>Item2</option>
</select>
<script>
$("#multiselect").kendoMultiSelect({
animation: false
});
</script>" to initialize? Is there a reason why mobile is being done this way vs the javascript way? My company used the javascript initialization way for almost all widgets since that was what the API documentation used to show. Is javascript initialization no longer working in mobile? Most of my widgets work fine still, but the modalView specifically behaves completely wrong when initialized in javascript. Styles don't get applied at all.
<a href="#my-modal" data-rel="modalview" data-role="button">Open Modal</a>
</div>
<div data-role="modalview" id="my-modal" style="width: 200px; height: 200px;">
Hello!
</div>
<script>
new kendo.mobile.Application();
</script>" as the new format for initializing widgets whereas the web documentation only uses "<select id="multiselect" multiple="multiple">
<option>Item1</option>
<option>Item2</option>
</select>
<script>
$("#multiselect").kendoMultiSelect({
animation: false
});
</script>" to initialize? Is there a reason why mobile is being done this way vs the javascript way? My company used the javascript initialization way for almost all widgets since that was what the API documentation used to show. Is javascript initialization no longer working in mobile? Most of my widgets work fine still, but the modalView specifically behaves completely wrong when initialized in javascript. Styles don't get applied at all.