Same issue here! I thought I was alone. It annoys me to no end and weirder still, issue doesn’t present itself with Firefox for Windows running behind the same IP.

Firefox Focus also doesn’t seem to present the issue. Just the primary Firefox browser for Android. And honestly, often enough that it’s nearly unusable.

If you ever figure it out, please let me know.

It’s always projection…so…

As a software engineer this is fascinating. Like, how would QC / QA have ever tested for this?

I mean, example, folding phones, it’s easy to just design a system that opens and closes it over and over. Samsung even has a butt sitting on testing device.

But testing whether the motion of a vehicle negatively impacts a wiring harness in some spot on the vehicle over time to cause this sounds rough. Again, though, I’m not in hardware jobs like these so maybe it’s actually easily caught?

Wherever is easiest to get up and out and go pee because I snuck in beer and I have a small bladder.

Love this explanation. Thanks much. Sharing…

I’m actually within about 5% ± on my Model S Plaid depending on the time of year and that’s hardly driving conservatively (maybe luck?). Oddly enough, my Model S has been more efficient than my Model 3 LR was, which I know makes no sense. But pretty much across the board for all the same drives, I use less kWh, it boggles my mind.

This is based on data from Tessie.

All that said, I realize the article says other manufacturers have more accurate fuel economies. I’m sorry, but no, my friend’s leaf is absolutely wrong by an extremely large margin, especially in winter, and has been since day one. It’s not even close.

This reminds me of when USAA would let you enter a longer password on the login screen than was actually possible to set, so if you generated a 14 digit password and pasted it into the password reset, it wasn’t immediately evident that it only took 12. But on login, you could enter all 14 characters and then it’d just say it’s wrong. I’m…90% sure they don’t do that anymore.

Also, KeyBank used to (or maybe still is? I closed my account years ago) not support case sensitive passwords. So whether your caps lock was on or not, or you alternated upper/lower however you wanted, your password still worked. I think they were converting to lowercase on the back end.

We could collectively vote to defederate them.