#Needs subsystem maintainer review

#18 this issue is about moving AWAY from ::commitAllOnShutdown() (and in general from committing during object destruction which has drawbacks).

IMHO, ::commitAllOnShutdown() should only be transitional towards such goal.

We now have \Drupal\Core\Database\Database::commitAllOnShutdown. Should we keep this issue open or change it somehow?

Believe this will need sub-maintainer approval for such a change, but could this functionality also live in a contrib module?

If approved will need an upgrade path and test coverage.

Done

shubh_ → changed the visibility of the branch 9.3.x to hidden.

shubh_ → changed the visibility of the branch 3239161-10.1.x to hidden.

shubh_ → changed the visibility of the branch 3239161-refactor-if-feasible to hidden.

For good practice can the MRs be cleanup/hidden. There are currently 4 branche

Went to review but appears MR has some failures

I tested the MR today and it works fine when I use the Images button (except the things discussed in the comments starting from #87).
I cannot get it working with the media library though. Is there anything that I need to keep in mind while testing it with the media library?

Confirming #141 patch works for

• Drupal 10.2.6
• PHP 8.2.12

mmunjeti → changed the visibility of the branch 1797438-html5-validation-is to hidden.

mmunjeti → changed the visibility of the branch 1797438-html5-validation-is to active.

Yes I think so too, it would be a good thing to add alongside a theme builder.

I also opened #3446582: Responsive images recipe → a couple of days ago, to ship some default image styles matching Olivero's break points to start with and linked this issue from there too.

I just read about the Starshot project. This issue could be related?