Hello Dimo,

thank you for pointing us to the Telerik status page overview yet again. But this is not helpful in all cases! I think a distinction has to be made between a feature request and a bug report: for a feature request, it is totally fine to prioritize this based on your product strategy and the customer demand.

But this, however, is a bug report. A component that already exists is not behaving the way it should be. And I am sure we can agree that fixing this would be trivial (making sure an integer cannot become less than 1 ...).

So we do not understand why this is not prioritized accordingly and instead mixed into the same pot with all feature requests and simply labelled as "Unplanned", without any indication as to when this will be fixed.

Background

Our own customers are more and more demanding full keyboard navigation support due to legal accessibility requirements, but we cannot in good faith turn this on for the TelerikTileLayout due to the numerous bugs we found. I hope you can understand that not even being able to at least communicate a broad time frame when they can expect this leaves us in a difficult situation.

Regards,
Alex

Hello all,

any updates on this one? Without this, the keyboard navigation of this component is basically unusable.

Regards,
Alex