Planned
Last Updated: 15 Sep 2021 11:16 by ADMIN
Scheduled for R3 2021 SP1

The issue is replicated in R3 2021 only. 

<telerik:RadTabStrip runat="server"  ID="RadTabStrip1" >
    <Tabs>
        <telerik:RadTab Text="Tab 1">
            <Tabs>
                <telerik:RadTab Text="fail"></telerik:RadTab>
            </Tabs>
        </telerik:RadTab>
        <telerik:RadTab Text="Tab 2"></telerik:RadTab>
        <telerik:RadTab Text="Tab 3"></telerik:RadTab>
    </Tabs>
</telerik:RadTabStrip>

Solution from Admin:

Place the load/script below somewhere under the ScriptManager. It can be added in the MasterPage if needed:

<script>
    Sys.Application.add_init(function fixTabStrip() {
        if (Telerik && Telerik.Web && Telerik.Web.UI && Telerik.Web.UI.RadTabStrip) {
            Telerik.Web.UI.RadTabStrip.prototype._childInserted = function (index, tab, owner) {
                this._allTabs = null;

                if (this._cachedSelectedTab) {
                    owner._setSelectedIndex(this._cachedSelectedTab.get_index());
                    this._cachedSelectedTab = null;
                }

                if (tab._cachedSelected) {
                    owner._setSelectedIndex(index);
                    tab._cachedSelected = false;
                }

                Telerik.Web.UI.RadTabStrip.callBaseMethod(this, "_childInserted", [index, tab, owner]);

                if (tab.get_isBreak()) {
                    var breakElement = document.createElement("li");
                    breakElement.className = "rtsBreak";
                    owner.get_childListElement().insertBefore(breakElement, tab._element.nextSibling);
                }

                //if (tab.get_parent() && tab.get_parent() instanceof Telerik.Web.UI.RadTab && tab.get_parent().get_selected()) {
                //    $telerik.$(tab.get_parent().get_levelElement()).removeClass("rtsHidden");
                //}
            }
        }
    });
</script>

Completed
Last Updated: 12 Aug 2021 14:38 by ADMIN
Release R3 2021
ADMIN
Created by: Attila Antal
Comments: 0
Category: TabStrip
Type: Bug Report
0
When adding a child tab programmatically to a second TabStrip tab that has no child item, the newly created child tab will not show up.

Workaround is to remove the class that was hiding the child element:

if (selectedTab.get_tabs().get_count() > 0) {
    $(selectedTab.get_levelElement()).removeClass("rtsHidden");
}
Completed
Last Updated: 12 Aug 2021 11:24 by ADMIN
Release R3 2021
Workaround: 

.rtsDropClueLeft {
    margin: -0.5em 0 0 -0.75em;
}

    .rtsDropClueLeft:before {
        content: "\e005";
    }

.rtsDropClueRight {
    margin: -0.5em 0 0 -0.25em;
}

    .rtsDropClueRight:before {
        content: "\e007";
    }
Completed
Last Updated: 11 Aug 2021 18:32 by ADMIN
Release R2 2017 SP1
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".
Completed
Last Updated: 13 Jun 2021 11:16 by ADMIN
Created by: Chris
Comments: 1
Category: TabStrip
Type: Feature Request
3
While it is currently possible to target the first or last item in a RadTabStrip via their CSS classes .rtsFirst and .rtsLast, it is not possible to target individual items, e.g. to add a custom icon or display different background images in tabs.

Assigning icons via the ImageURL property is often not feasible, e.g. when using the RadTabStrip-based navigation controls in Sitefinity.

Numbering the list items, e.g. .rtsLI1, .rtsLI2, .rtsLI3, etc., would be trivial to implement and provide a lot of flexibility through individual CSS targeting.

This also applies to the RadPanelBar and RadMenu controls.
Declined
Last Updated: 28 May 2021 17:49 by ADMIN
Please see the ticket here http://www.telerik.com/account/support-tickets/view-ticket?threadid=1010098.

I still need to support IE8 browsers.  The removal of the frameBorder attribute from the iframe rendering causes layout issues in IE8.  Adding a property to the RadPageView project to re-enable this behavior would fix this issue.  It could be false by default in order to pass the cited validation tool.  The developer would have to enable the property in order for the frameBorder attribute to be rendered as frameBorder="0".
Completed
Last Updated: 17 May 2021 15:05 by ADMIN
Release R2 2021 SP1
ADMIN
Created by: Veselin Tsvetanov
Comments: 1
Category: TabStrip
Type: Bug Report
1

			
Unplanned
Last Updated: 22 Apr 2021 15:53 by ADMIN

Tab Strip scroll buttons do not work in RTL mode in Chrome. The issue can be reproduced here:

Scrolling and Multi-row Tabs Online Demo

 

Video:

http://somup.com/crf3odFFjF

Unplanned
Last Updated: 01 Dec 2020 16:15 by ADMIN
Created by: Bryan
Comments: 0
Category: TabStrip
Type: Feature Request
1
Refer Support Id 1122136  
( https://www.telerik.com/account/support-tickets/view-ticket?threadid=1122136 )
for screen shots and explanation...

Where we use the ShowBaseLine property in Horizontal Orientation, the same feature is not available when in Vertical Orientation
Unplanned
Last Updated: 13 Nov 2020 08:35 by ADMIN

Steps to reproduce:
Use the code below. Select the Members tab and press the tab key - nothing happens. Focusing the DataPicker is expected.

  <a href="http://www.google.com">Google</a>

    <div class="RadTabStripWrapper">
        <telerik:RadTabStrip ID="rtsCommitteeTabs" runat="server" MultiPageID="rmpCommitteeTabViews" RenderMode="Lightweight">
            <KeyboardNavigationSettings CommandKey="Alt" FocusKey="T" />
            <Tabs>
                <telerik:RadTab PageViewID="pvMeetings" Value="Meetings" Text="Meetings">
                </telerik:RadTab>
                <telerik:RadTab PageViewID="pvMembers" Value="Members" Text="Members">
                </telerik:RadTab>
                <telerik:RadTab PageViewID="pvAttributes" Value="Other Information" Text="Other Information">
                </telerik:RadTab>
                <telerik:RadTab runat="server" PageViewID="pvCommitteeLinkDocTab1" Text="Link Doc Tab 1" Value="CommitteeLinkDocTab1">
                </telerik:RadTab>
                <telerik:RadTab runat="server" PageViewID="pvCommitteeLinkDocTab2" Text="Link Doc Tab 2" Value="CommitteeLinkDocTab2">
                </telerik:RadTab>
                <telerik:RadTab runat="server" PageViewID="pvCommitteeLinkDocTab3" Text="Link Doc Tab 3" Value="CommitteeLinkDocTab3">
                </telerik:RadTab>
            </Tabs>
        </telerik:RadTabStrip>
    </div>
    <div class="RadMultiPageWrapper">
        <telerik:RadMultiPage ID="rmpCommitteeTabViews" runat="server">
            <!-- Meetings Tab -->
            <telerik:RadPageView runat="server" ID="pvMeetings" CssClass="MeetingsTab">                
            </telerik:RadPageView>
            <telerik:RadPageView runat="server" ID="pvMembers" CssClass="MeetingsTab">
                <telerik:RadDatePicker ID="datePickerMeetingsFrom" CssClass="DatePicker" runat="server" RenderMode="Lightweight" EnableAriaSupport="true" EnableKeyboardNavigation="true" aria-label="From date for the meeting date range filter">
                    <DateInput runat="server" ValidationGroup="MeetingDates" aria-label="From date for the meeting date range filter">
                    </DateInput>
                </telerik:RadDatePicker>
            </telerik:RadPageView>
            <telerik:RadPageView runat="server" ID="pvAttributes" CssClass="MeetingsTab">
            </telerik:RadPageView>
            <telerik:RadPageView runat="server" ID="pvCommitteeLinkDocTab1" CssClass="MeetingsTab">
            </telerik:RadPageView>
            <telerik:RadPageView runat="server" ID="pvCommitteeLinkDocTab2" CssClass="MeetingsTab">
            </telerik:RadPageView>
            <telerik:RadPageView runat="server" ID="pvCommitteeLinkDocTab3" CssClass="MeetingsTab">
            </telerik:RadPageView>
        </telerik:RadMultiPage>
    </div>

    <a href="http://www.google.com">Google 2</a>

Completed
Last Updated: 21 Oct 2020 15:39 by ADMIN

JAWS reads Tab selected when the focus is moved between tabs without selection:

<telerik:RadTabStrip ID="RadTabStrip1" runat="server" MultiPageID="RadMultiPage1" EnableAriaSupport="true" RenderMode="Lightweight" SelectedIndex="0" TabIndex="0">
    <KeyboardNavigationSettings CommandKey="Alt" />
    <Tabs>
        <telerik:RadTab runat="server" Text="Root RadTab1">
        </telerik:RadTab>
        <telerik:RadTab runat="server" Text="Root RadTab2">
        </telerik:RadTab>
        <telerik:RadTab runat="server" Text="Root RadTab3">
        </telerik:RadTab>
        <telerik:RadTab runat="server" Text="Root RadTab4">
        </telerik:RadTab>
        <telerik:RadTab runat="server" Text="Root RadTab5">
        </telerik:RadTab>
    </Tabs>
</telerik:RadTabStrip>

Completed
Last Updated: 21 Oct 2020 15:39 by ADMIN
Release R3 2020 SP1
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

Completed
Last Updated: 16 Oct 2020 17:16 by ADMIN
Release R3 2020 SP1
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: 12 May 2020 12:28 by ADMIN

Scenario: RadButton within RadPageView part of RadMultiPageView integrated with RadTabStrip for switching PageViews.

When switching tabs, additional padding is applied to the text in RadButton. After a postback is made, padding is not applied anymore.

 

 

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.
Completed
Last Updated: 03 Sep 2019 16:13 by ADMIN
Release R3 2019
Created by: Sunil Sutar
Comments: 2
Category: TabStrip
Type: Bug Report
1

Hi Telerik team,

 

Few of our clients reported the following issue with respect to WCAG 2.0 SC 4.1.2 standard. (508 Standard and compliance) -

PracticeFunction (example)
Ensure ARIA roles, states, and properties are validLI has an aria-level attribute of 0, which is not an integer value greater than, or equal to, 1

 

Example: visit https://demos.telerik.com/aspnet-ajax/tabstrip/examples/wai-aria-support/defaultcs.aspx 

 

Observe the ul-li elements created for tabstrip. On each li element, there is aria-level attribute whose value is set to 0.

As per WCAG this value should start from 1. The value 0 is invalid. Refer: https://www.w3.org/TR/WCAG20-TECHS/ARIA12.html

 

Please let me know when are you going to fix this for compliance. 

--

Sunil

Completed
Last Updated: 03 Sep 2019 16:12 by ADMIN
Release R3 2019

Few of our clients reported the following issue with respect to WCAG 2.0 SC 4.1.2 standard. (508 Standard and compliance) -

 
Practice Function (example)
Ensure sub-lists are marked up properly This UL should only contain li elements (without an ARIA-assigned role), script elements (without an ARIA-assigned role) or template elements (without an ARIA-assigned role); or
 
elements with a role=listitem attribute; as direct child elements

 

Example: When Telerik Tabstrip has EnableAriaSupport=true, internally tabstrip is combination of ul-li with css to display the Tabs properly -

The html looks like as follows -  

<ul class="rtsUL">
    <li class="rtsLI rtsFirst" role="tab" aria-disabled="false" aria-level="0" aria-controls="LayoutPageView">
        <a accesskey="L" title="Layout" class="rtsLink rtsBefore" id="LayoutTab" href="#"><span class="rtsOut">
            <span class="rtsIn">
                <span class="rtsTxt">
                    <h2 class="RadTabStrip RadTabStrip_Default"><u>L</u>ayout</h2>
                </span>
            </span>
        </span>
        </a>
    </li>
    <li class="rtsLI" role="tab" aria-disabled="false" aria-level="0" aria-controls="SearchPageView" aria-selected="true" id="SearchTabStrip_active_tab">
        <a accesskey="S" title="Search" class="rtsLink rtsSelected" id="SearchTab" href="#">
            <span class="rtsOut">
                <span class="rtsIn">
                    <span class="rtsTxt">
                        <h2 class="RadTabStrip RadTabStrip_Default"><u>S</u>earch</h2>
                    </span>
                </span>
            </span>
        </a>
    </li>
    <li class="rtsLI rtsLast" role="tab" aria-disabled="false" aria-level="0" aria-controls="ResultsPageView">
        <a accesskey="R" title="Statewide Search Results 0 records" class="rtsLink rtsAfter" id="ResultsTab" href="#">
            <span class="rtsOut">
                <span class="rtsIn">
                    <span class="rtsTxt">
                        <h2 class="RadTabStrip RadTabStrip_Default">Statewide Search<u>R</u>esults (0)</h2>
                    </span>
                </span>
            </span>
        </a>
    </li>
</ul>


Observe the aria attributes which are on li elements. Is that really necessary considering the compliance? (as mentioned in practice and example).

 

Please let me know when are you going to fix this for compliance. 

--

Sunil 

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.
Completed
Last Updated: 17 Apr 2018 15:16 by ADMIN
Workaround is attached. It focuses the first focusable element on the page and you can easily change that logic.


We have already taken upon ourselves the task of managing the keyboard navigation in a container (the pageview).

Please leave your comments how this should be fixed, because there are many options. For example:

   -  we can focus the first focusable element, in a fashion similar to the workaround. Caveat: the list is incomplete, there are more focusable elements. Also, non-sequential tabIndex values set by the developer will not be honored. We may implement logic that counts the tabIndexes and focuses the smallest one, but this is complex, error prone and browsers tend to return bad values for this attribute, especially when it is set to -1. Also, this may not be the desired behavior by the developers.

    - we can focus the pageview element. Caveat: you may be unable to enter its child inputs at all, depending on the page setup and the tabIndex values.

    - we can consider setting tabIndex to -1 for all focusable elements in other pageViews akin to the modal backgrounds for controls like window and tooltip. The goal being to let the natural flow of the page take over and the browser to do this job, not our JS code. Caveat: we can still break the navigation logic on the page and this also has low performance when changing many tabIndex attributes at once.
1 2