mike-000

> I cannot seem to reproduce this issue. I'm running `npm run test-rendering -- --interactive --match webgl-reproj-no-wrap` and panning around. Maybe a webgl context was dropped? I can reproduce reliably...

> I am just seeing this. I have tried on more devices and get different results depending on the device.

That is probably an improvement as it was necessary to stretch in canvas without interpolation to avoid corrupting floats, see #15885. Maybe add a new test **webgl-reproj-float-interpolate-false** which should produce...

> > I am just seeing this. > > I have tried on more devices and get different results depending on the device. In a polar projection source tiles from...

> The issue concerning max texture size with stitch images should be fixed now. Yes, some artefacts are visible at times because of the reduced quality, but that is better...

@tschaub The console suggests that might be a network problem with that source file. I do not see any problems with Multiple COG Sources or STAC Support example which also...

The OpenLayers map defaults to the device pixel ratio when it is constructed. Browser zoom increases the device pixel ratio but does not change an existing map. If necessary you...

> I don't want to increase the pixel ratio for the entire Map By zooming in, refreshing, then zooming out again you were setting the map pixel ratio to 2.2222...

That would be a breaking change because any code which currently specifies `crossOrigin: null` would need to be changed to ``no-cors``. It would be simpler to simply fix what seems...

Currently `undefined` means use the default setting. `null` always means use no CORS, and needs to be specified if the default is different. OSM is similar to KML. If you...