Maybe TypeError is better....? about web-share HOT 2 CLOSED

The spec is using TypeError to indicate that the sharing site has a bug or is incompatible with the User Agent. This isn't the case here.

Excluding this case, the spec is using AbortError when the user does not choose a share target. The user will know that they have not completed the share; the sharing site does not need to display an error
message.

The main reason for considering a different exception here would be if the sharing site should report a specific error message. However, the user agent or operating system can give the user a more informative error message than the sharing site can. Thus every sharing site shouldn't need to consider detecting and reporting an error for this rare case.

AbortError is reasonable as, from the sharing site's perspective, the user simply didn't successfully complete the share.

from web-share.

"If an error occurs starting the target or transmitting the data" seems like this will be a user agent, OS or target specific error. It might be caused by the data (for example, a target might reject if the text contains non-ASCII characters), or it might be any other transient error (like the target crashed on startup). A TypeError should be a specific problem with the data, as defined by the spec, which isn't the case here.

from web-share.