andwati/kget-capture
1
0
Fork 0
mirror of https://github.com/andwati/kget-capture.git synced 2026-10-18 03:02:56 +00:00
Code Issues Packages Projects Releases Wiki Activity
12 Commits 1 Branch 7 Tags
79b72494db4213b17bfad29d9e72077e63f71824
Commit Graph
6 Commits
Author SHA1 Message Date
andwati 79b72494db Bump version to 1.0.5 2026-08-12 15:10:33 +03:00
andwati 6ed564f802 Bump version to 1.0.4 2026-08-12 14:36:25 +03:00
andwati a2cd4184e3 Don't hand file:// URLs to KGet 
Ctrl+S on a page you navigated to directly via file:// is still a
"download" as far as chrome.downloads is concerned, so auto-capture
was intercepting it and handing the local path to KGet, which
rejects it with a confusing "protocol is not supported" dialog since
it's a network download manager, not a file copier. Extend the
existing blob:/data: exclusion to also cover file:/filesystem:, and
apply the same guard to the right-click capture path.
 2026-08-12 12:11:03 +03:00
andwati 235c377361 Fix Chrome save-as prompt and unreliable finish notifications 
Chrome's own "Ask where to save each file" setting shows a native
picker before the extension can ever intercept the download, and no
extension API can read or suppress it -- surface this clearly in
install.sh, the README, and a popup shortcut instead of leaving it
buried as a footnote.

Also fixes silently missing "download complete" notifications: KGet
only fires its own finished-notification if a transfer was observed
in a non-finished state at least once, so small/fast downloads that
complete before that first observation never get one. The native
host now drives its own notification via notify-send, polling actual
transfer progress instead of relying on KGet's internal check, and
install.sh disables KGet's own notification to avoid duplicates.
 2026-08-12 11:33:46 +03:00
andwati c395c5fbe2 Bump version to 1.0.1 2026-08-12 10:01:26 +03:00
andwati ef70a20093 initial commit 2026-08-12 09:02:09 +03:00