stephent

See also #2881 and https://issuetracker.google.com/issues/198562471

OK - so this is traceable back to bad CSS in Google Maps. See https://stackoverflow.com/a/69031991/220287 Here's a separate branch ([css-patch](https://github.com/stephent/react-google-maps-markers/tree/css-patch)) of my reproduction with the patched CSS applied, which functions...

So, it seems that the underlying issue here is related to using `preventGoogleFontsLoading: true`. [Response](https://issuetracker.google.com/issues/206864372#comment3) from Google engineers: > Upon checking it seems like that "react-google-maps-api" prevents certain Maps JS...

See https://github.com/stephent/react-google-maps-markers/tree/dont-prevent-google-fonts-loading for demo of workaround, also deployed here: https://react-google-maps-markers-git-dont-preven-672625-stephentrainor.vercel.app/?v=weekly

I'm seeing a very similar issue in my create-react-app since 3.46 went into weekly in early September (I'm pinned at 3.45 as a temporary workaround). Markers are no longer draggable,...

Seems this is due to CSS conflicts - see https://github.com/JustFly1984/react-google-maps-api/issues/2906#issuecomment-973058108

I saw that @plouc expanded the initial issue I reported, but like @cfecherolle I'm only using `@nivo/core` and `@nivo/line` also, so I believe they (or one of them) should be...

I've found that none of my listeners will fire in a release build, although they work as expected from the debugger. Adding implementation "org.jetbrains.anko:anko-sdk25-listeners:0.10.8" doesn't seem to fix it. I...

As a workaround to this, I'm cheating the selected date by offsetting the actual date/time of my application's state by the utc offsets of the user's default time zone and...

@swkre @JohnStarich I think generalizing it beyond just UTC would be preferable. I have a use case where the time zone of the control should match the time zone of...