As mentioned earlier, if you send an image through the WhatsApp Web interface in Pale Moon, the image loads and displays fine. So there is no problem displaying locally cached images (which is probably why the workaround described here works), but some problem downloading and displaying remote images.
I tried looking at the resulting HTML for some clue, and compare "good" and "bad" instances. The good instance looks something like this:
Code: Select all
<div class="bubble-image bubble-image-caption">
<div style="width: 330px; height: 138px;" class="image-thumb">
<img style="height: 100%;" class="image-thumb-body" src="blob:63418730-7d77-4527-bd65-767d997706a1">
</div>
[MESSAGE DATA SKIPPED]
</div>
Code: Select all
<div class="bubble-image bubble-image-caption">
<div style="width: 330px; height: 185px;" class="image-thumb">
<div class="media-state-controls">
<button class="icon-xl icon-media-cancel">
<svg style="width: 50px; height: 50px;" viewBox="0 0 43 43" class="spinner-container">
<circle strkeo-width="3" fill="none" r="20" cy="21.5" cx="21.5" class="path"></circle>
</svg>
</button>
</div>
<img style="height: 100%;" class="image-thumb-body image-thumb-lores" src="data:image/jpeg;base64,[INLINE JPG DATA SKIPPED]">
</div>
[MESSAGE DATA SKIPPED]
</div>
In the good case, the image source is loaded from some blob. I am not familiar with this syntax, and what it means. For whatever reason, something breaks when the WhatsApp web client in Pale Moon is trying to load a remote blob.
Hopefully someone experienced in these web technology may get an idea from this data what can be going wrong. I sure cannot.