Re: [w3ctag/design-reviews] EyeDropper API (#587)

I'm becoming more convinced that `AbortError` in the event of the user canceling the operation is the wrong response (and the File System Access API is wrong too). 

Even given the case if it should be agreed that user cancellation is an exceptional situation (which I do not agree with), a different error should be thrown. I believe `AbortError` should be exclusively used in response to an `AbortSignal`.

I'm also beginning to strongly feel that the `open()` method should accept an `AbortSignal` via an options dictionary, e.g. `open({signal: signal})`. This allows not only a clear mechanism for the caller to abort the operation, but for surrounding code to pass in an `AbortSignal` of its own.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/587#issuecomment-911901194