As a front-end developer, I'd expect the ability to customize the fallback <img> tag HTML output inside the <picture> tag would work the same way as with non-responsive images.
I'd expect to be able to add theme suggestions for the image template based on the image style_name used in the fallback and ideally the responsive image style id would also be present.
/**
* Implements hook_theme_suggestions_HOOK_alter().
*/
function THEMENAME_theme_suggestions_image_style_alter(array &$suggestions, array $variables) {
$suggestions[] = $variables['theme_hook_original'] . '__' . $variables['style_name'];
}
/**
* Implements hook_theme_suggestions_HOOK_alter().
*/
function THEMENAME_theme_suggestions_image_alter(array &$suggestions, array $variables) {
$suggestions[] = $variables['theme_hook_original'] . '__' . $variables['style_name'];
}
However, the responsive_image module does not send the style_name parameter to the image template. And, similarly Drupal core currently doesn't provide a way to pass along the responsive_image_style_id to the various image templates.
responsive_image_style_id as an optional variable sent to all image templates involved in the responsive image render chain. In cases where the image template is not part of a responsive image, the variable would default to NULL.<img> tag.
None.
A new theme template parameter called responsive_image_style_id will be introduced for the image, image_formatter, and image_style theme functions. The variable will be available to template suggestion hooks, theme preprocess hooks and inside the Twig templates.
None.
Needs work
10.1 ✨
Last updated
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request → as a guide.
This was previously tagged for tests in #4 which still needs to happen.