mike-000

@ahocevar That does not fix it. I think the underlying problem is `this.lastAnchor_` stores a coordinate. If it stored the event pixel `map.getCoordinateFromPixel(this.lastAnchor_)` could be used in the timeout handler.

`moveend` firing seems like a separate bug - presumably because the interaction uses `view.beginInteraction()` and `view.endInteraction()` around trackpad timeouts but not for wheel. But fixing that might not prevent this...

> Something happens between the end of `handleWheelZoom_` and the start of the next `handleEvent` `zoomByDelta(view, delta, this.lastAnchor_, this.duration_)` changes the center if the anchor is not at the center...

With default flag settings:  Going to about://flags and changing ANGLE backend from `default` to `D3D11` fixes this (Max Varying Vectors increases to 30) but that is not something an...

It is still happening in https://openlayers.org/en/main/examples/webgl-vector-layer.html on system/browser combinations which default to D3D9, where it can be fixed via the about://flags/#use-angle workaround. The affected systems are not Windows 11 compatible...

It looks like you intend to accept reproj tiles in the composite instead of reprojecting composite sources? In that case should the composite projection be the view projection and the...

Passing the projection from the renderer's `getTile` request onto the component sources is correct. Projection and tilegrid should be set null in the composite source setup. The renderer will call...

Be aware that currently if the requested projection is equivalent to `source.getProjection()` `getTileGridForProjection()` returns `source.getTileGrid()` (if set) regardless of what was set for the projection using `setTileGridForProjection()`. #15988 would change...

In the example it looks like the OSM is not interpolated. Is it possible to handle the different interpolate settings of the original sources?

See #16000 It should be fixed in version 10.0.0