feat: custom TitleBar with window controls (no native decorations) #7
@@ -12,6 +12,13 @@
|
|||||||
"fs:allow-read-file",
|
"fs:allow-read-file",
|
||||||
|
|
|||||||
"fs:allow-read-dir",
|
"fs:allow-read-dir",
|
||||||
"fs:read-files",
|
"fs:read-files",
|
||||||
"fs:read-dirs"
|
"fs:read-dirs",
|
||||||
|
"core:window:allow-minimize",
|
||||||
|
"core:window:allow-maximize",
|
||||||
|
"core:window:allow-unmaximize",
|
||||||
|
"core:window:allow-close",
|
||||||
|
"core:window:allow-start-dragging",
|
||||||
|
The capabilities add The capabilities add `core:window:allow-maximize` and `core:window:allow-unmaximize`, but the UI code introduced here only calls `toggleMaximize()` (plus `minimize()`, `close()`, `isMaximized()`). To keep least-privilege, consider removing permissions that aren’t required for the current implementation (unless Tauri’s permission model for `toggleMaximize` implicitly depends on them).
|
|||||||
|
"core:window:allow-toggle-maximize",
|
||||||
|
"core:window:allow-is-maximized"
|
||||||
]
|
]
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user
core:window:allow-start-draggingis added to the capability set, but the UI code in this PR doesn’t callstartDragging()anywhere (and also doesn’t currently usedata-tauri-drag-region). If dragging will be handled via the HTML attribute, consider removing this permission; if dragging will be handled via the API, add the corresponding call in the title bar so the extra permission is justified.