OpenStars

I highly doubt that this orders search results like it did ten years ago ignoring SEOs though. This looks to only fix the latest category of screw-up.

It cannot be done - enjoy it, this is your life now.

On the one hand, there are true alternatives like Vimeo. On the other, sometimes you just need to access an existing video...

Um... tech-bros, apparently? :-(

Not the particular web developer I had in mind, who prefers raw JS and resents having to use libraries, but sadly yeah far too common it's that, for basically no other reason than that - like, there's other ways to make "pretty" and "functional":-(. The web has truly enshittified, and I'm glad Firefox is still fighting against it.:-)

Damn that's amazing - thanks so much for sharing it with us!:-)

I've heard web developers say that a lot of that is due to Firefox's annoying (to them) choices.

I happen to know HTML, CSS, & raw JS even though nothing at all from the last roughly decade, and I guarantee you that I can, and have, written webpages that work on any browser. More to the point, Firefox does not fully support HTML5 - and while tbf none of the browsers do(:-P), it does lag noticeably behind. Then again, it has made major pushes forward in terms of security... though seemingly at the cost of its basic functionality, to the point where if you want to use some even moderately complex coding framework, then you pretty much have to use Chrome.

So what I do is use Firefox for personal use, and Chrome at work. I then also use Chrome at home for personal use, unless I want to view a commercial site (where ads make every experience not only slower but practically unusable imho). Sadly, that's the only option I have, if I want to be able to "view websites".

In the past, Microsoft used to encourage features that would work only in their shitty-AF browser. But I got the sense that this is not what is happening now, b/c it's simply HTML5 - did Google somehow have some "in" with whoever designed that, hoping to give themselves an edge?

Anyway, I use Firefox, but I wish it was better.:-( I'm always so frustrated with it that I keep telling myself I will replace it someday, perhaps with LibreWolf?

That's likely it. Weirdly, turning off that feature may not make all that much of a difference, bc it's so incredibly rare, but if you don't need it - like a long press of the power button would do just as well, in the also rare event that you want to turn it off at all - then disabling that feature would give you peace of mind.

Either way, I'm glad I could help by giving you the idea of how to (maybe) fix it!:-)

The frequency of this issue happening probably varies per person like depending on pockets and usage patterns and such. Like nowadays when I go cycling I either put the phone into an attachment on the front of the bike, or after that broke I put it in my backpack, and either way it never randomly turned off. And in my old Nexus where the issue did happen, the headphone jack working to pull the phone up more than it would have done all on its own probably contributed. i.e., for some people it will never be a problem with their patterns, but if it is for you, then presuming that's it, disabling that power-off feature (if you can) should make you much more satisfied!:-)

Thanks for the additional feedback!:-) That does greatly reassure me.

Since you said the phone would come right back on immediately thereafter, it sounds to me like it does not seem connected to the battery issue.

Unless the battery issue wasn't "really" a discharge but the sensor somehow being tricked into thinking that the battery was dying - in which case the phone likely shut down gracefully rather than risk a brown-out situation, but then when you powered it up later it realizes once again that it has battery.

But in a more normal scenario, if you have either tap-to-wake or if hitting the power button results in a screen prompt confirmation that does not require a fingerprint or PIN, and especially if you were walking or cycling or some such, then the screen likely rubbed up against your pocket lining and managed to cause the proper combination of actions to shut it off. It could not start up an app that way - that would need your login - but turning a device off usually requires lesser security.

Fortunately the latter may be possible to fix with a configuration setting or other software fix:-).

For food. You know... nom nom (the humans as food I am hinting at!:-P).

So on a scale of 1-5, responsiveness might be a 4?

About the design, I mean like a poorly-placed power button that is easily triggered (and then whatever confirmation procedure is in place can be performed by your pocket), or the sudden drainage of battery issue could be something about poor Quality Assurance when they pick batteries at the factory to put into the devices prior to shipping them out. Or worse, you could replace the battery and that effect could still happen!?

I had a Nexus 5 that would dial things, like even emergency #s (fortunately I don't think it would actually do the call, just dial the numbers) while in my pocket - it may have had something to do with turning the screen on while a headphone jack was plugged into it. I replaced the OS for other reasons and that happened to solve that issue as well:-). So I would not turn a phone away for such a thing, especially if there is a software/configuration fix.

But responsiveness is as much due to hardware as software - e.g. if Firefox runs slow b/c it was compiled for and websites (even mobile) designed for higher-end specs.