Evert Eti

Thank you for your response. Is this on purpose? Would there be a way or option to enable this to get closer to the real tail behaviour?

I was trying to build a GDAL POC, where I encountered the following `ERROR 1: PredictorSetup:Horizontal differencing "Predictor" not supported with 64-bit samples` Could it be that this is the...

Should be working since https://github.com/sindresorhus/notifier-for-github-chrome/pull/123 due to the `window.addEventListener`.

@weiwancheng Did you solve this problem?

This issue is also affecting our codebase. Is there any shortterm planning for a fix or should we also use `correlationHeaderExcludedDomains` in the meanwhile?

Using these properties would indeed help to solve this. But wouldn't there still be a problem needing to convert `map.centerX and map.centerY` back and forth, possibly introducing slight errors?

Since xToLon, yToLat aren't exported in the default export, it might be easier for us to calculate the center ourselves. And render the first map with center + addBound (undocumented?)...

1. Would having a `centerLat` and `centerLon` property on the map next to `centerX` and `centerY` be acceptable? 2. Would you be open for a PR documenting `addBound`?

@jpvajda To me it seems to be a different issue but I am not very experienced with apollo yet.

#10105 is closed but the problem persists in last version