-
Notifications
You must be signed in to change notification settings - Fork 177
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
overflowbutton #399
Comments
I also encountered the same problem, Is there any method to place overflowbutton before customization? |
I believe I am facing the same issue. In my code, I have added some custom buttons to the tabSet header (by pushing them onto renderValues.buttons within my onRenderTabSet function) , but now the overflow button shows up after those custom buttons, instead of right after the tabs, and this is not intuitive. I have been unable to find a way to modify the positioning of the overflow button so far; it seems to always show up after the custom buttons I have pushed on to the renderValues.buttons array. Would appreciate it if there was a way to modify the overflow button's position in the order of the tabSet toolbar buttons. |
Actually, looking around, I found a solution to the problem, using css. Look at the first answer at the following link, that recommends using css flexbox's To apply this solution to flex layout, I noticed that all of the tabSet header buttons are contained with a div that has the class |
Thanks, I'll give it a try |
v0.7.10 moves the overflow button to before the custom buttons (but after sticky buttons) |
Describe the bug
I was hoping to modify the position of the overflowbutton, and now the position of the overflowbutton is fixed after the custom button, which is not actually visual
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
empty
Expected behavior
I would like to modify the location of the overflowbutton
Operating System
windows
Browser Type?
chrome
Browser Version
106
Screenshots or Videos
empty
Additional context
No response
The text was updated successfully, but these errors were encountered: