Comment 9 for bug 1531913

Ultimately it's the call of whoever wrote the API and what was their intention. I tend to agree that the fallback is only meant to deal with cases where the scope can't do anything about it. When sending empty, it might very well send the fallback URL instead.

What's the argument against the above? Maybe it's API and/or docs that need to be amended to make it more clear?

I'm not saying no, but it's not our decision alone.