Completed
Last Updated: 20 Nov 2014 20:00 by ADMIN
Created by: JohnVS
Comments: 2
Category: SPA
Type: Feature Request
53
Currently, there is no way to make a Mobile Application (SPA) search engine friendly. You cannot use the "alternate" and "canonical" tags, since the SPA page is only loaded once. And you can't use Google's suggested #! syntax, since Kendo only supports the # syntax. So there is basically no way to get a Kendo Mobile website indexed properly.
Completed
Last Updated: 07 Oct 2016 12:21 by ADMIN
Created by: alon
Comments: 2
Category: SPA
Type: Feature Request
10
Missing a real world sample of spa with shell's page + layers with AngularJS like we have in mvc/jsp/php demos.
why spa (the most common used) have no samples, no blogs, no documantation with - AngularJS ? 
Completed
Last Updated: 22 May 2014 12:36 by ADMIN
Created by: Imported User
Comments: 1
Category: SPA
Type: Feature Request
10
Add a small nanoscopic progress bar featuring realistic trickle animations to convince your users that something is happening. This would be perfect for Turbolinks, Pjax, and other Ajax-heavy SPA's.

More infos: https://news.ycombinator.com/item?id=6246183
Completed
Last Updated: 17 Jul 2014 15:21 by ADMIN
Created by: Christian
Comments: 1
Category: SPA
Type: Feature Request
10
Some animations for Kendo view transitions in the Web UI would be awesome. SPA's are missing that nice fade or slide between view switching. 
Completed
Last Updated: 26 Nov 2014 16:54 by ADMIN
Created by: Imported User
Comments: 2
Category: SPA
Type: Feature Request
1
Kendo editor should change it's size according to the text inside the text area if the relevant option is set to "true"
Completed
Last Updated: 25 Nov 2014 14:50 by ADMIN
Created by: Imported User
Comments: 1
Category: SPA
Type: Feature Request
1
Kendo editor should have an option to change it's colour tool (ex:- "websafe", "basic" etc.)
Completed
Last Updated: 11 Aug 2016 19:04 by Marc Simkin
Created by: Marc Simkin
Comments: 3
Category: SPA
Type: Feature Request
1
The routing framework should allow the developer to choose either the legacy # base routing scheme or the new HTML5 routing and History API.

This would make the porting of applications from other frameworks (AngularJS, Backbone, etc) that already support HTML5 routing easier.
Completed
Last Updated: 30 Oct 2017 17:22 by ADMIN
Created by: Steve
Comments: 2
Category: SPA
Type: Feature Request
1
With Vue.js integration started but not complete, I'd like to see the plan for rolling out the integration until it has parity with the existing packages like jQuery & Angular.  I'd also like information about any public beta versions so that I can plan for controls as they appear.  I have a possible long term upcoming project that I'd like to consider using these controls in, but without visibility into the progress it will be hard to justify using this package.