Unplanned
Last Updated: 03 Jan 2020 15:07 by ADMIN

In the RadMultipageView a portal URL is set as content. The user navigates to one of the pages within the portal. Now there is no way to go back to previous page or to the default landing page where the tab was initially at.

Requesting a new feature in the tab strip to allow navigate through the iframe history (back/forward) for a multipage view. It could be similar to the back/forward buttons of the browser but within the tab of the tab strip where the content URL is set in the multipage view. This could be set enable/disable by a setting.

Unplanned
Last Updated: 02 Jan 2020 16:31 by ADMIN
Created by: Lou
Comments: 1
Category: TabStrip
Type: Bug Report
0
The tabs will scroll by themselves even when your finger is off the screen.
Unplanned
Last Updated: 31 Oct 2019 11:54 by ADMIN
Created by: Jeff
Comments: 1
Category: TabStrip
Type: Bug Report
0

Accessibility Insights is reporting invalid markup on all tabs in the TabList.

When consulting the online aria specifications I see that elements with role="tablist" support aria-level="#" where number is > 0.  (https://www.w3.org/TR/wai-aria-1.2/#tablist) However, elements with role="tab" do not. (https://www.w3.org/TR/wai-aria-1.2/#tab)

If possible, we would like to see the aria-level tag moved to the correct page elements in the next release. (Thanks for correcting the aria-level="0" problem previously.) 

I believe this may be the compliance issue Sunil was reporting previously here: https://feedback.telerik.com/aspnet-ajax/1413112-this-ul-should-only-contain-li-elements-without-an-aria-assigned-role

Unplanned
Last Updated: 02 Aug 2019 10:12 by ADMIN
Only the selected tab has an aria-selected attribute. According to the documentation I can find, all tabs should have aria-selected, and be set to true or  false as appropriate.
https://www.w3.org/TR/wai-aria-1.1/#aria-selected

aria-selected (state)§

Indicates the current "selected" state of various widgets. See related aria-checked and aria-pressed.

This attribute is used with single-selection and multiple-selection widgets:

  1. Single-selection containers where the currently focused item is not selected. The selection normally follows the focus, and is managed by the user agent.
  2. Multiple-selection containers. Authors SHOULD ensure that any selectable descendant of a container in which the aria-multiselectable attribute is true specifies a value of either true or false for the aria-selected attribute.

Any explicit assignment of aria-selected takes precedence over the implicit selection based on focus. If no DOM element in the widget is explicitly marked as selected, assistive technologies MAY convey implicit selection which follows the keyboard focus of the managed focus widget. If any DOM element in the widget is explicitly marked as selected, the user agent MUST NOT convey implicit selection for the widget.

Characteristics:
CharacteristicValue
Used in Roles:
Inherits into Roles:
Value:true/false/undefined
Values:
ValueDescription
falseThe selectable element is not selected.
trueThe selectable element is selected.
undefined (default)The element is not selectable.
Unplanned
Last Updated: 09 May 2019 07:55 by ADMIN
We are using the Telerik tabStrip ASP.NET AJAX control.

We have set PerTabScrolling="true" on the tabStrip.

Then we have hidden a tab on the client side that is apart of the tabstrip.

Now when we scroll to the end of the list we receive a JavaScript error: Sys.InvalidOperationException: Cannot serialize non finite numbers.

This only happens when we hide a tab.

 
Unplanned
Last Updated: 27 Jul 2017 07:47 by ADMIN
ADMIN
Created by: Veselin Tsvetanov
Comments: 0
Category: TabStrip
Type: Bug Report
1

			
Unplanned
Last Updated: 30 May 2017 08:41 by ADMIN
The disabled tabs don't look like disabled in Classic render mode. 

This issue is not observable with the 2016 release as shown in the attached screenshot.

Workarounds:
1) You can change the color of the disabled items by applying the following class to the page:

        .rtsLink.rtsDisabled {
            color: #a5a5a5 !important;
        }

2) Another option is to switch the rendering to Lightweight -> RenderMode="Lightweight".
Unplanned
Last Updated: 06 May 2014 07:21 by ADMIN