diff options
Diffstat (limited to 'docs/superpowers/plans/2026-08-03-post-0.1.0-usability-closed.md')
| -rw-r--r-- | docs/superpowers/plans/2026-08-03-post-0.1.0-usability-closed.md | 11 |
1 files changed, 9 insertions, 2 deletions
diff --git a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability-closed.md b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability-closed.md index 4f361bf..a4aae42 100644 --- a/docs/superpowers/plans/2026-08-03-post-0.1.0-usability-closed.md +++ b/docs/superpowers/plans/2026-08-03-post-0.1.0-usability-closed.md @@ -5286,8 +5286,15 @@ returning `nullptr` discards it before it can be read. Routing it through the same handler the plain-link path uses is what keeps the two kinds of link from drifting apart. -127: three actions added to `removeBrowserActions()`'s list, -`CopyLinkToClipboard` deliberately left. The order mattered: 126 gives the page +127: four actions added to `removeBrowserActions()`'s list, +`CopyLinkToClipboard` deliberately left. The fourth, `DownloadLinkToDisk`, was +added after a hand test: it had been deferred to item 114 alongside Save image +on the grounds that both are inert without a `downloadRequested` handler. True, +and the wrong conclusion. Save image is content the message already carries; +Save link fetches a sender-chosen remote URL through the one profile that must +never fetch remote content, so it is removed rather than implemented, and item +114 now carries the constraint that a handler for the former must not revive the +latter. The order mattered: 126 gives the page a real `createWindow()`, so those entries would have stopped being merely dead and started opening links into a tab that does not exist. |