Pressing ctrl-F doesn’t refocus the search field if there is already a search term, it only focuses search on 1st open of the search field. This PR fixes it so that every time the user presses CTRL+F, the search field is focused again.
Tested on linux.
Reviewed-on: https://codeberg.org/ArkHost/HelixNotes/pulls/216
- Add entitlements.plist for Developer ID hardened runtime (JIT,
unsigned memory, library validation, network client)
- Reference entitlements in tauri.conf.json bundle.macOS
- Guard get_install_type() with early mobile return (avoids
std::process::Command in iOS binary)
- Add cfg(mobile) no-op branch to xdg_open()
Code blocks used a hardcoded 13px font-size instead of scaling with --editor-font-size, so they didn't resize with the rest of the editor content when zooming.
Reviewed-on: https://codeberg.org/ArkHost/HelixNotes/pulls/208
Launching with a custom dark theme left every divider in light-theme colors until you re-toggled the theme in Settings.
`applyTheme` was copy-pasted across the components and the copies drifted. Three of them (+page.svelte's onMount block, AppLayout.svelte, NoteWindow.svelte) had no custom-* branch, so for a custom theme they stripped the dark class and data-theme attribute, matched nothing, and fell back to the bare light :root values.
`+layout.svelte` applied the custom theme correctly, but `AppLayout` — the always-mounted shell — re-runs its own broken copy from an `$effect` on `$theme`, immediately wiping it out. Dividers gave it away because custom themes override `--border-color` but not `--border-light`, which dividers use.
Fix: consolidate into a single `applyTheme`(which already owns darkThemes/isDarkTheme) with a real `custom-*` branch, and have every call site use it and pass the loaded custom themes so `custom-*` ids resolve.
Reviewed-on: https://codeberg.org/ArkHost/HelixNotes/pulls/200
Yuri Karamian