Picture Display Lacking on 33.1.0 and 33.2.0

[NapoInRags]

Hello,

(Still) running 10.11 El Capitan on a 2008 Macbook.

Here is the Pitchfork website home page with Pale Moon : the pictures are missing.

Capture d’écran 2024-06-19 à 23.05.30.png

By comparaison, the complete page (from Chromium Legacy) :

Capture d’écran 2024-06-19 à 23.07.14.png

Is there a way to fix that ?

Thanks.

[Kris_88]

You can try userContent.css :

Code: Select all

@-moz-document domain("pitchfork.com") {
  .aspect-ratio--overlay-container { position: relative !important; }
}

[NapoInRags]

Firstly glad to identify the userContent.css file,
then impressed to see that it works !

But, isn't there a way to integrate this code in the browser code itself, for it to display directly this website properly, and the numerous ones certainly in the same situation ? Or is there a reason not to do this ?

[Moonchild]

But, isn't there a way to integrate this code in the browser code itself, for it to display directly this website properly, and the numerous ones certainly in the same situation ? Or is there a reason not to do this ?

First, it would make for a huge and unwieldy stylesheet to load everywhere. That's not a good idea.
Second, who would maintain such a thing?

[NapoInRags]

I don't know much about coding and I had imagined, not a stylesheet to complete website after website, but a generic code that would apply everywhere, as it must be case with browsers for recent computers.

But your answer obviously shows it's not possible.

[Moonchild]

But your answer obviously shows it's not possible.

the workaround is just that: a workaround. It can be solved but it has to be solved in a different way, i.e. implementing whatever the website is assuming every browser supports (I'm guessing by the name it'd be the CSS aspect-ratio keyword in this case). It's on the to-do in that case, but I'm currently not sure when we'll get to it as it's not the only thing we're missing or implementing differently than Chrome and Chrome-clones.

[NapoInRags]

I welcome with pleasure the userContent workaround, but my original intention, however poorly formulated, was to draw the Palemoon team's attention to this display problem. If it's on your to-do, then it's perfect.
Congratulations for your great job.