The arguments to the function were bad. If ERR_BAD_ARG is returned synchronously, it indicates that a sanity check on the arguments failed and the function wasn't called (the handler will still be called with { error: ERR_BAD_ARG }, and possibly additional information). When ERR_BAD_ARG is received by a handler, it indicates either a warning or an error.

The method has been deleted. This is always an error. When passed to the handler, errorMsg may contain information for debugging.

The method has been deprecated. This is a warning, never an error. If this is passed to a handler, errorMsg will contain useful information about the action you should take.

ERR_NONE will be zero for this version and future versions.

A cross-frame communication failure occurred.