[Tabs] Forced Scroll Buttons don't work
See original GitHub issueIn the Tabs component, when trying to have forced scroll buttons visible, it still uses the default behavior of only showing the scroll buttons when needed.
- [✓] The issue is present in the latest release.
- [✓] I have searched the issues of this repository and believe that this is not a duplicate.
Current Behavior 😯
scrollButtons: "on"
is ignored or doesn’t work properly
Expected Behavior 🤔
Scroll buttons should always be visible
Steps to Reproduce 🕹
Steps:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (8 by maintainers)
Top Results From Across the Web
[Tabs] Forced Scroll Buttons don't work · Issue #22181 - GitHub
In the Tabs component, when trying to have forced scroll buttons visible, it still uses the default behavior of only showing the scroll...
Read more >Sheet tab scroll buttons don't work in excel 2010
In my Excel 2010 file there are three sheets. I can navigate between them by clicking on the sheets on the bottom left...
Read more >Scroll buttons do not appear until new tab loaded - Telerik
I have a radTabStrip inside a radWindow. Scrolling on the tabstrip is set to true. When I resize the radWindow the scroll buttons...
Read more >Material-ui Tabs - how can I put scroll of them - Stack Overflow
I am using Material-ui Tablist for my in my AppBar component. The problem is that I have too many Tabs and I want...
Read more >Use tabs in Chrome - Computer - Google Support
Unpin a tab: Right-click the tab and select Unpin. Move a tab to a different window: Make sure both windows are signed in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sure! I’ll submit a PR with an update to the docs.
@oliviertassinari Thanks Olivier. It seems the other demos had been passing in
classes.root
to the surroundingdiv
instead of passing in theclasses
property directly to theTabs
component. Cheers for that. PR Incoming.