Position the markers relative to the map panes.
Don't position the element that contains the markers.
Renamed all the geo service projection methods, for clarity.
Because the parent node of marker has size 0x0, top 50% and right 50% would affect nothing. You only need to translate(-50%, -50%) to move it to the right position.
Fixes an issue where, even if the end user has a proper google maps API
mock, the GoogleMaps component will throw an error when in a test
env. ReactDOM.findDOMNode(this.googleMapDom_) returns `null`.
This commit wraps the subsequent addEventListener call in an `if` block,
ensuring that an empty DOM doesn't add complications to test suites
* Option to position components with two corners.
This lets you lock a component to a specific bounding rectangle, which allows for precise tiling during zoom.
* Add a comment explaining two point positioning.
* Use the experimental version, to get the new zoom animation.
* Don't use bounds for rendering in 3.32
* Revert the project() and unproject() methods.
Instead, add a new method fromLatLngToContainerPixel() to geo service.
* No need of setting .exp, that is by default
* Comments explaining the significance of API v3.32
* Add _VERSION to const
Added an if statement in onRemove() function that checks if "this.div" is defined before calling ReactDOM.unmountComponentAtNode(this.div). This is done to avoid throwing an "unmountComponentAtNode(...): Target container is not a DOM element" error. I ran into this error while using google-map-react with React Router and switching between tabs rapidly to stress test my application.
* Move heatMap docs to API.md
* Upgrade example code style
* Specify that we need a container in the example
* Actually, remove propTypes, will confuse ppl
* Add more instructions
* Add main title
* Quick corrections
* Add PRs welcome status
* Move features down
* Actually, lets not use PFC, will avoid confusions
* Remove center from tips, its obvius
* Remove bower message, not needed I believe
* Clearer documentation
* Create our own createHelper, its not in recompose anymore
* Use our withStateSelector
* Proper apiKey usage
* Replace apiKey with bootstrapUrlKeys
* No need of true value in html
* Use lodash.omit instead in dev
* Remove unused file
* Remove unnecessary extra folder utils
* Upgrade recompose again
* Oops! Move lodash.omit to devDependencies
* Fix webpack files styles
* Make examples bigger in width
* Use shallowCompare to compare objects
* Use isEmpty as much as possible
* Use our own shallowEqual
* Remove fbjs
* Just disable necessary line
* Add eslint-disable where needed
* Use pure reduce and map functions
* Use only isEmpty from lodash
* Create our own isEmpty, don't use lodash
* Normalize utils names
* Group utils together
* Proper checking, better this way
* Set default value to options
* fix error about fromLatLngToDivPixel
fix "Cannot read property 'fromLatLngToDivPixel' of undefined" #257
* skip only the code that relates to div or overlay
* added intellij ide gitignore
* IE9 and IE10 require loose to work
your demo app doesn't work on IE9/10 so you will need to make a more simple one to test this fix out. the issue is to do with this.props not being avaiable in constructors for IE9/10 see: https://github.com/babel/babel/issues/3975 it was supposidly fixed 1 year ago but I can't see it working, maybe we need to swap to @babel/core to get this fix? I tried it but the change is made larger due to the curent demo apps build system.
Full fix would involve upgading to @babel/core + @babel/preset-env and migrating away from kotatsu in favour of a plain ole react app via webpack (create-react-app maybe?) and then place it into another folder and have that folder habing it's own package.json so we can consume google-map-react as if it were a real library during testing. Sure we would loose hmr, but at this stage hmr isn't all that useful anyway.
I'de love the proper fix, but for now I have clients with IE10 browser requirements.
