Completed
Last Updated: 31 Jul 2023 14:21 by ADMIN
ADMIN
Dess | Tech Support Engineer, Principal
Created on: 07 Dec 2018 10:47
Category: UI Framework
Type: Bug Report
0
FIX. API documentation - incorrect links and very slow searching experience
After revamping the documentation for the Telerik UI for WinForms product, the following problems occurred:

1. Search for a specific class or method in the search box in the following site: https://docs.telerik.com/devtools/winforms/introduction. Select one of the results referring to the API documentation. As a result you will be navigated to the main page of the API reference instead of to the respective class or method. Refer to the Problem1.gif file. It seems that the search results from the API reference return old links for the previous API link pattern.

2. The search box in https://docs.telerik.com/devtools/winforms/api/ is significantly lagging while typing. We should consider performing the search operation after pressing Enter and not with each keystroke. Please refer to the Problem2.gif file.

3.  When you scroll the navigation view on the left side to a certain position and select an article, the vertical scrollbar sometimes gets reset to the top position and you have to scroll back.  (Note that this problem is not reproduced each time).
Attached Files:
2 comments
ADMIN
Dess | Tech Support Engineer, Principal
Posted on: 31 Jul 2023 14:21

Hi,

All of the listed 3 topics have been addressed and with the latest version of the API documentation it is expected to behave correctly.

 

Regards,
Dess | Tech Support Engineer, Principal
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Desislava
Posted on: 05 Jun 2019 12:30
I would like to follow up with an update:

1. API redirects have been added to navigate toward the respective class instead of the API index page.

2. There is an auto-filter delay now. If the user is typing quickly, the filtering will start after approximately 0.5 s after the last entered character, not on each key stroke. This will improve the filtering performance.