Although I did not manage to crash my browser, you will need to remove the k-input CSS class before instantiating a widget from a DOM element. This is because the k-input CSS class is intended for in-widget-use only and the widgets do not expect this CSS class to exist initially. Their behavior is to try to copy the initial CSS classes from the textbox to the widget wrapper, which will result in a k-input class applied to an element that should not have it.
You can use a k-textbox CSS class for standalone <input> elements (it is better than k-input), however, this also needs to be removed before widget initialization.
the Telerik team
Join us on our journey to create the world's most complete HTML 5 UI Framework - download Kendo UI