Well...
I believe it's the documented behaviour, so, I guess so?
In practice, I think it's (at least in part) a consequence of trying to make a "one size fits all" sort of API to cover the supported platforms, and "embracing" the vagaries of the different interfaces we need to wrap. You can never please everybody, it turns out.