As you can see from the image below the tab strip tabs can keep getting added and they do not care where the parent DIV or any other container ends. It would be appropriate for them to allow for scrolling if it goes outside the width of its container.
This is the way it is handled in jQuery
It should be possible to apply missing semantic information to the rendered code of a web application to support handicapped users to get the most possible benefit of the Kendo UI framework.
Should have features on previous web technologies. What's the point of going new, if features are missing?
Once in a while, I try out a new Version to see, whether performance has improved. and constantly, I find that this is not the case. The best treeshaking technique from Angular is spoilt by KendoUI components because of all the millions of bytes of script code that get downloaded by your components and lead to a desastrous client experience! Optimization would be as simple as a good redesign. I wonder, why this still did not happen over the last year!
hi guys, We are debating between ag-grid for Kendo ui angular 2....what better to use? 1. Does Kendo UI grid supports RTL (Right To Left)? 2.How to implement expandable row In ag grid angular 2 ? 3. How to implement paging In ag grid angular 2