[cap-talk] getting authorization from the user and the great insight

[David Hopwood]

James A. Donald wrote:
> Karp, Alan H wrote:
>  >> Actually, typing in the window containing the text
>  >> could be a good way to denote that you want to grant
>  >> write authority to a file previously opened read
>  >> only.
> 
> David Hopwood wrote:
>  > Yuck, no. It's far too easy to press a key
>  > accidentally when focus is on the window. Better to
>  > have a "Edit this file" entry in the context menu (the
>  > one obtained by clicking the window icon on the left
>  > of the title bar).
>  >
>  > There are several other functions that need to be
>  > intermediated by the trusted window system, such as
>  > the cut/copy/paste menu entries, and the "Recent
>  > files" list. If they are moved to the context menu,
>  > then no user confirmation is needed. If they are in a
>  > menu controlled by the app, then I can't see any
>  > secure way to avoid a redundant confirmation.
> 
> Redundant confirmations are never acceptable.

So move these functions to the context menu.

(I don't agree that redundant confirmations are *never* acceptable,
but in this case we have a solution that is both secure and avoids
redundancy.)

-- 
David Hopwood <david.hopwood at industrial-designers.co.uk>