Could this be a bug caused by the fact that I have two screens (Moto Razr+)?

Doubt it. This happens a lot for me too on a boring single-screen S23.

I assumed it was crappy devs not testing on FF anymore & have lived with it (since it’s a pain to debug css/js problems on mobile).

Next time I see it happening I’ll reproduce on desktop FF with responsive emulation & report the bug.

The first report I looked at was Entrust refusing to revoke certs because their clients’ manual processes would make applying reissued certificates inconvenient.

Quite fun reading, surprisingly - a mid thread revelation that they’d pulled the exact same shit 4 years ago, an attempt by Entrust to kill the issue because unattributed legal advice said they’d misreported the error. And then, just when their chutzpah seemed to be wearing everyone down, a good ‘fuck you’ from Apple forced them to revoke the certs after all.

I’m not surprised Google had enough & yanked their license to print money.

Totally OK way of doing it. You basically manually implemented the protocol APIPA uses to allocate 169.254 addresses.

It’s pretty close already. I forget where I cribbed the technique from, but I embed python functions into my scripts very often…

E.g. see here