4 ms·
Sadly this kind of lockout is implemented client-side in Javascript. Either by actively nerfing the FF performance (if ff then bad perf), or by using APIs known
by tuetuopay 4y ago
Sadly this kind of lockout is implemented client-side in Javascript. Either by actively nerfing the FF performance (if ff then bad perf), or by using APIs known to be bad on firefox. All of Google's websites are a perfect example of both actually (no proof needed, but I cannot believe it's only the second option).
- withinboredom 4y agoTo get you to use Edge, Windows nerfs Chrome’s background performance by shunting all the processes on to a single core (or it used to) randomly. You can’t fucking win. I wouldn’t be surprised if Apple does something similar to Chrome/Edge.
- culi 4y agoI don't think Apple does, but I've noticed stuff like the touch bar and the finger print reader prompting to automatically sign in on certain sites only work on Safari. It makes sense that Safari would be better integrated with the OS. Not sure if it's a matter of Apple not making the API available to other browsers or them not taking advantage of it though
- themoonisachees 4y agoAFAIK touch bar is application-controlled, so its up to chrome/ff to use the API to make it work.