Problem/Motivation

I am currently writing tutorials about how to use Drupal 8. While trying to explain things to newbie Drupal users, I found that IMage handling in Drupal 8 core seems odd and not that userfriendly in many situations.

Let say you install Drupal Core 8 from scratch. You have been advertised Drupal8 to be fully responsive from scratch but then you discover there are two modules images: Images and Responsive Images.

A/ Why needed two modules that from a naive user perceptive does the same (let you display images with nice formatter), but the second one better than the first one !?
Debate : from less naive user, you would say the first one let's you create some image styles that can be used in the responsive image settings. Here are possible solutions :
i.: Merge both modules
ii.: Rename Image to Image Style and let it be the module handling "the transformation and serving of images in Drupal". Rename Responsive Image to Image and let it be the module "define a responsive image field". Because actually well... Image have to be responsive nowadays. NOTE that if no breakpoints are sets, it could be easy to fall back to the behavior of Images here.

B/ Enable Responsive Image by default: Drupal is said to be responsive, let the image be too by default !!
Action:
1. enable Responsive Image module by default.
#1855412: Enable responsive_image.module by default for standard install profile

C/ Create default configuration for Responsive Image module. Because when you enable it and you already have a working image field (per instance the default image field in article), your first move is to set this image field formatter to "responsive"... and get a weird error.


Actions:
1. Create default Responsive Image Style configuration
#2513604: Create default responsive image styles

D/ Because there are no responsive image style set, I got a weird error here.
Actions:
1. Change the error message in the form (see above) for "I'm am the site administrator" !!
2. Change the general error message (see below): what am I supposed to do with this responsive image style link ? How about a more specific message ?

EDIT: wow, actually that links to this very same form... Hum.. that was so unclear then !
3. Add a link to Responsive Image style just as per the simple Image formatter (see below)

#2534074: Update error messages in field formatter when no Responsive Image Style available

E/ Well... let's create a Responsive Image Style then. What is a fallback image ? Is that the default image style used by the field, like the one used by default for the largest display ? Is that the image style used for the lowest size: ie the image it fallback when on mobile ?
Action:
1. add a description meaningfull description to this option.
#2534066: Allow selecting the original image when creating a responsive image style

F/ Then, before saving, I am requested for image style to use for each breakpoint. What is None ? A naive user would need to do the mental gym to find what is implied.
Action:
1. Rename option "None" to "Native image".
#2534066: Allow selecting the original image when creating a responsive image style

Proposed resolution

See above

Remaining tasks

- debate each point if needed
- implement the sub-issues listed above.

User interface changes

- yes: that is the point

API changes

Point A would lead to a lot of disruptive changes, thus to be debated

Data model changes

Point A would lead to a lot of disruptive changes, thus to be debated

Comments

dom.’s picture

Issue summary: View changes

Added link to sub-issues.

rainbowarray’s picture

These are all good suggestions. Thanks for pulling them all together here!

It's pretty late in the D8 cycle to consider changing the name of the Image module or merging the Image and Responsive Image modules. I think both of those suggestions have merit, but I doubt we can accomplish big changes like that at this point.

Enabling the Responsive Image module by default seems like a more realistic possibility.

Please also note that #2334387: UI changes to support current responsive image standards should also help with some usability issues.

attiks’s picture

Category: Bug report » Plan

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

gaëlg’s picture

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.