You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Toolbars have been a primary reason for responsive issues in a lot of Tyler apps. They don't scale down well on smaller screen sizes without a lot manual CSS or DOM manipulation. I think we can standardize this to handle a majority of use cases. We could provide a breakpoint value and a list of options as configuration options, and the toolbar would use container queries to handle the UI swapping. The most common scenario is tucking forge buttons that are in the end slot into a simple forge-menu at a certain size. Screenshots below:
Large screensize:
Smaller size:
The text was updated successfully, but these errors were encountered:
Toolbars have been a primary reason for responsive issues in a lot of Tyler apps. They don't scale down well on smaller screen sizes without a lot manual CSS or DOM manipulation. I think we can standardize this to handle a majority of use cases. We could provide a breakpoint value and a list of options as configuration options, and the toolbar would use container queries to handle the UI swapping. The most common scenario is tucking forge buttons that are in the end slot into a simple forge-menu at a certain size. Screenshots below:
Large screensize:

Smaller size:

The text was updated successfully, but these errors were encountered: