Warning rying to access array offset on value of type null in Drupal\media_responsive_thumbnail\Plugin\Field\FieldFormatter\MediaResponsiveThumbnailFormatter->viewElements()After updating from 8.x-1.2 to 8.x-1.3

Looks like the lazy image loading stuff was only added in 10.1.x, so my mistake was applying the fix from #3322231 without specifying the different version required.

Could you check out the newest dev branch and report if that fixes it? If so, I can push the next release.

dev branch solves the problem. Can you push to next release?

Thx

The dev branch did not solve this issue for us on Drupal 9.5. We had to revert back to 1.2.

Here are the logs:

Message Deprecated function: pathinfo(): Passing null to parameter #1 ($path) of type string is deprecated in Drupal\image\Entity\ImageStyle->addExtension() (line 505 of /sites/dev/cms/releases/20230222200847/web/core/modules/image/src/Entity/ImageStyle.php)

Deprecated function: pathinfo(): Passing null to parameter #1 ($path) of type string is deprecated in _responsive_image_build_source_attributes() (line 380 of /sites/dev/cms/releases/20230222200847/web/core/modules/responsive_image/responsive_image.module)

Could not determine image width for '' using image style with ID: 1024. This image style can not be used for a responsive image style mapping using the 'sizes' attribute.

The dev branch worked for us on Drupal 9.5.3. Just to be completely sure, after I installed the dev version of the module, I rebuilt caches via drush and rechecked the page where I saw the warning. The warning didn't appear, and I didn't see anything in the logs or status report page.

I suppose I'll consider this fixed, since #7 looks unrelated.

@yoruvo I am still trying to debug this. Something has changed in the output which causes issues in Drupal 9.5.3.

Automatically closed - issue fixed for 2 weeks with no activity.

Hi Yoruvo,
the issue by itself is indeed fixed, but it would be nice to provide a setting in media_responsive_thumbnail formatter to manage loading attribute.
Should i create a feature request for that ?