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
How to make the function buttons (maximize, minimize, close) on the toolbar keep the characteristics of their respective operating systems (windows on the right, macos on the left), while being able to customize the toolbar. Because when developing an APP, the layout of the APP sometimes has a menu bar on the left and display content on the right, without a toolbar, but the three buttons in the toolbar (maximize, minimize, close) need to be retained.
Describe the solution you'd like
Refine the setting of "decorations: false". When it is currently set to false, the toolbar and function buttons disappear at the same time. It is expected to add a reserved operation button
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
On macOS you can use the titlebarStyle window config and for Windows we're waiting on an update from WebView2 tracked here #4531 / MicrosoftEdge/WebView2Feedback#4532
These configs will keep just the control buttons while removing the titlebar (so you can create your own if needed)
Describe the problem
How to make the function buttons (maximize, minimize, close) on the toolbar keep the characteristics of their respective operating systems (windows on the right, macos on the left), while being able to customize the toolbar. Because when developing an APP, the layout of the APP sometimes has a menu bar on the left and display content on the right, without a toolbar, but the three buttons in the toolbar (maximize, minimize, close) need to be retained.
Describe the solution you'd like
Refine the setting of "decorations: false". When it is currently set to false, the toolbar and function buttons disappear at the same time. It is expected to add a reserved operation button
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: