mike-000

If feature styles and style objects are to be deprecated soon I presume an API compliant workaround such as ``` feature.setStyle(new VectorLayer({style}).getStyleFunction()) ``` to share flat styles used elsewhere will...

This is the current behaviour of TileWMS - a fixed WMS request bbox is used. When `hidpi` is requested the pixels added will be the request gutter multiplied by the...

It is only inconsistent in the constructor, where it has a different purpose. As long as `getGutterForProjection()` returns pixels added (taking the map pixel ratio into account if necessary, and...

They are inconsistent because they have different purposes. One should be (the `hidpi` option uses the map pixel ratio even when it is less than one which seems wrong) the...

i.e. `gutter: 20,` would become `ratio: 296 / 256,` in the current wms20 tests? In which case a `getGutterForProjection()` override would still be needed (taking account of the `ratio` and...

Marking this as ready for review, since any changes to functionality of a source which does not have a `tilePixelRatio` option (but does use `getTilePixelRatio()`) are beyond the scope of...

It would be possible to use user coordinates (a breaking change) if the current behaviour is considered a bug, but the "extent" would not be a true bounding extent in...

For any source type you can use ``` const key = source.on('change', () => { if source.getState() === 'ready') { unByKey(key); // source is ready } }); ``` For a...

If you zoom in and out the map switches from arctic to antarctic and back again. It is using cached reproj tiles for the wrong projection. This appears to have...

#16141 will fix this https://deploy-preview-16141--ol-site.netlify.app/en/latest/examples/reprojection-by-code.html