- π«π·France prudloff Lille
We encountered this problem as well but I don't think
native_lazy_loading_preprocess_image()
has enough context to know where the image will be displayed (or even to know which field it comes from).
I think the solution will be to use the new functionality from core ( π¬ Comparison with Drupal Core lazy loading, future of this module Active ) as it can be enabled/disabled on each field.