Changelog for v6.5.0
This commit is contained in:
@@ -1,10 +1,10 @@
|
||||
## Upgrade notes
|
||||
|
||||
### Next version
|
||||
### v6.5.0
|
||||
|
||||
#### Units of the `hitTolerance` option fixed
|
||||
|
||||
Previously, the `hitTolerance` option of the map's `getFeaturesAtPixel()`, `forEachFeatureAtPixel()` and `hasFeatureAtPixel()` methods behaved differntly depending on the `devicePixelRatio` (or the `pixelRatio` of the map), because the original value was internally multiplied by the device pixel ratio twice instead of just once. Now this is fixed. **Note**: The `hitTolerance`'s units are css pixels. The documentation was updated to reflect this.
|
||||
Previously, the `hitTolerance` option of the map's `getFeaturesAtPixel()`, `forEachFeatureAtPixel()` and `hasFeatureAtPixel()` methods behaved differently depending on the `devicePixelRatio` (or the `pixelRatio` of the map), because the original value was internally multiplied by the device pixel ratio twice instead of just once. Now this is fixed. **Note**: The `hitTolerance`'s units are css pixels. The documentation was updated to reflect this.
|
||||
|
||||
If your application adjusts for that with code like
|
||||
```js
|
||||
|
||||
Reference in New Issue
Block a user