Which browser(s) was this tested with?

We already handle rejections from ResourceLoader; I don't think there is anything more we could do about this. MediaViewer will recover properly from the BSOD once bug 66598 is fixed (thanks for reporting that!).

On second thought, probably better to leave this open until the upstream issue is fixed.

(In reply to Andre Klapper from comment #1)

Which browser(s) was this tested with?

Firefox, Chrome and Opera.

Now the MultimediaViewer shows a error message with a close button. RESOLVED and WORKSFORME

Bug 66598 is still not fixed, so remove dependency.

Retested. Still exist.

While pending requests and failed server responses is outside MultimediaViewer, I think the immediate bug at hand is that MultimediaViewer is setting up an empty and confusing interface for the user (black overlay, with no way to exit, or indication what is happening) that is then indefinitely presented until an asynchronous process has finished.

I'd recommend improving the logic flow on the client-side first to prevent that situation from occurring that way in the first place. E.g. by providing a way to escape and a progress indicator, or by setting up the overlay separately and not attaching it to the page until it is ready.

I'd recommend improving the logic flow on the client-side first to prevent that situation from occurring that way in the first place. E.g. by providing a way to escape and a progress indicator, or by setting up the overlay separately and not attaching it to the page until it is ready.

Depending on the situation, the setup phase can take long, which is very confusing if there is no visual indication; having the overlay is better, There is no way to get a progress ratio for much of the delays involved; I guess we could display an indeterminate progress bar after a second or so. Opened T86288 about this.

It would definitely be nice to have some sort of cancel option, e.g. having the close button in place as soon as the overlay appears. Unfortunately the overlay is created by the bootstrap module and the close button by the full module, so that would require a fair bit of refactoring or some messy hacks. I opened T86287 to track this.

Mass-removing the Multimedia tag from MediaViewer tasks, as this is now being worked on by the Reading department, not Editing's Multimedia team.

I still can reproduce the bug as described in the description.

Before rMW103eb48ac20e: ResourceLoader: Set module state "error" if request fails on network the screen gets black.
After rMW103eb48ac20e: ResourceLoader: Set module state "error" if request fails on network there is a flash of a black screen.