📦 Preview the website for this branch here: https://deploy-preview-16262--ol-site.netlify.app/.

Thanks for your contribution, @MrLynx93. I think something is wrong here: The pull request title makes sense, but it is already possible to combine layers and filter. Your change here changes things so it is possible to combine layers/filter with features, which would not work.

By the way, using a features collection would probably be a good way to fix your problem in #16261. If there is something to improve the Translate interaction, it would be to make it work with a source as an alternative to features, like the Draw, Modify and Snap interactions do.

Thanks for the quick response @ahocevar . My problem is that I do pass in features and layers both. But layers are ignored because of this line: if (options.layers && !this.features_) which assigns layerFilter_ only if you didn't pass in features.
I edited the title of this pull request to make this more clear.

So what's the point of using both features and layers? Why don't you just pass features, e.g. from a source you created with useSpatialIndex: false?