Hi, some of you noticed our Bing maps imagery layers aren’t working this morning, we’re working to get that resolved quickly.
I have a question for the community about what our default behaviors should look like. Obviously if an imagery layer throws errors, the widget should catch that and swap in another layer as a backup. But I have a question about what to do before layer 0 (the base layer) has loaded:
Imagine the case of a user, with a local CZML file, but only the poorest-quality dial-up access to his imagery provider. Layer 0 is coming down, just not soon, and his CZML has already finished loading, so his loading screen has disappeared. This could happen to a remote mobile user perhaps. The imagery layer isn’t going to throw an error, it will work… eventually. Our current behavior is not to render any tiles, so the Earth is transparent to the star background behind it. Should we change this to render a default solid color, like dark blue or black, instead of skipping the render?
Sure, users on fast connections will see a blink of dark blue or black while they wait for level 0 to load, but today they’re seeing a blink of star background during that same interval. If they’re stuck looking at that sorry state for any length of time, I’d offer that a solid color would be preferable to the star background by a wide margin. I think this is more in line with how web behavior in general works, where the browser tries to render as best it can while pieces are still loading.
Should we make this change?