Need More Info
Last Updated: 15 Jul 2024 07:33 by ADMIN
Created by: Paul
Comments: 3
Category: TabStrip
Type: Bug Report
0

I recently received an email from one of our users stating that the scroll buttons on the tabstrip have stopped working. I have just upgraded to Angular 17 and latest of progress controls so not sure if that is what did it but these buttons have been working since implementation.  I am puzzled as to what is now missing and or caused the buttons to stop working. They do display correctly when the screen size changes and not all tabs are on the screen. However, when you click either forward or back, nothing happens.

I anticipate that I will be asked to create a reproduction of this and send it to kendo, but was hoping that someone could take a look at our application to see if something is missing or if it can be determined what is causing the issue? This is a huge application and depends on data to run so it would take quite some time to get it down to something I can send as a repro.  See page  https://test.tropicos.org/name/25509881.

What makes it worse is that we also have another application that was spawned from the shell the Tropicos app and for the most part uses the same packages. This application also gets updated at the same time as Tropicos as well.  This application however is not seeing the same problems with tab strip buttons. See https://test.livingcollections.org/taxon/277173

If I must spend the time to strip the application down to a page that causes the issue, I can. But, again, this would take quite a bit of time and we are a small development shop so hoping looking at the apps I posted will help to find the issue.

Completed
Last Updated: 16 May 2024 11:17 by ADMIN

The "auto" scrolling mode of the TabStrip works fine when we resize the container or the window - i.e. the scroll buttons appear if the tabs do not fit ij the container. However, they do not appear if we add tabs dynamically and this is a bug. If we add tabs dynamically, then once the tabs dont fit in the container, the scroll biuttons should appear. Below is the example in stackblitz:

https://stackblitz.com/edit/angular-p5jc7v?file=src%2Fapp%2Ftab_content.ts,src%2Fapp%2Fapp.component.ts

Completed
Last Updated: 21 Mar 2024 13:28 by avto

After updating to Angular version 17.3.0 the TabStripComponen throws errors:

  • Error: Failed to execute 'setAttribute' on 'Element': 'aria-disabled]' is not a valid attribute name.
  • Error: Cannot read properties of undefined (reading 'filter')

The problem can be reproduced using this StackBlitz sample: https://angular-baaosj.stackblitz.io

Declined
Last Updated: 27 Jul 2021 11:40 by ADMIN
In TabStrip control with angular 7: when moving to another tab and hitting ngAfterViewInit() on that tab's component -> previous tab's component still exists - showing 2 components together.
Declined
Last Updated: 22 Jan 2019 08:59 by ADMIN
Created by: Christopher
Comments: 1
Category: TabStrip
Type: Bug Report
1

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

https://demos.telerik.com/kendo-ui/tabstrip/scrollable-tabs