Alex von Brandenfels

As I understand it, returning an immediate failure in browsers with third-party cookies disabled is intended behavior and it's coming from Google's code, not from react-google-login.

Something like this worked for me: ``` const ExampleComponent: React.FC = () => { const globeMethods = useRef(undefined); return globeMethods.current?.pointOfView({lng: -90, lat: 30})} />; ```

The workaround suggested in @ConnorsApps comment above will break click functionality for normal mouse users, which my application needs to work, so I added detection of iOS to the below...

That all makes sense, I agree it should only be in strict/stylistic after all

The well-defined and expected behavior for calling `Number.isNaN` on a non-number is just `return false`, which makes sense because the JavaScript implementation of this function has to do _something_ if...

Any usage of a predicate where the result can be known at compile time is pretty suspicious, but as you point out, there's currently no way in TypeScript to detect...

I just ran into this issue with not being able to stash the changes as well (wanted to switch branches). I was able to solve it by just committing the...

I'm having this issue as well. We are on version 5.10.4

I found some more info on this bug and a workaround in https://github.com/mui/material-ui/issues/31869 > The problem exists because mobile Safari fires mousedown as a way to emulate mouse events. The...