Shall we keep or drop custom breakpoints? Your vote counts

Created on 9 January 2020, over 4 years ago

Updated 3 September 2023, 10 months ago

Problem/Motivation

I am happy to announce that Responsive image integration is almost 90% done with the latest work here:
#3097685: Support aspect ratio for Responsive image →

The remaining 10% is to make the Responsive image work with Blazy CSS background.
This is still a question -- the only reason the custom breakpoint is still kept for now. Multi-breakpoint CSS backgrounds with Responsive image is still tough to cope with (due to picture + too many unpredictable breakpoints which Blazy script itself might not be able to deal with correctly, CMIIW). Yet was already done with custom breakpoints since likely early developments

On the other hand, the custom breakpoints do share at least 200 lines as seen at \Drupal\blazy\BlazyBreakpoint. Temporary solution was already provided as an option via Blazy UI to just disable these lines. Meaning you are being facilitated to a great extent, you can disable it if you don't use CSS background, nor custom breakpoints.

And now you are also being facilitated to drop it for good.

There are so many modules with CSS background images, but many are not multiple-breakpoint responsive nor lazyloaded -- another reason to keep Blazy CSS background feature around. I am shocked that I found so many just now:

Proposed resolution

Second opinions are needed and very much appreciated:
Shall we keep or drop custom breakpoints?
If dropped, please suggest a solution based on the above problems. Perhaps joining forces with one of them, and drop Blazy?
If kept, why?

Please continue, ignore my absence, if you don't see me reply to your comment. I would try to refrain replying to avoid bias for now, and let it flow. You are given situations above, feel free to share your thoughts. I will again ask you before I decide anything after having enough representatives whatever it will be.

Thank you in advanced!

Remaining tasks

Not sure to deal with this, but perhaps a vote for keep or drop?
If so, please state your opinion with reasons, or even just +1 (keep) or -1 (drop).

User interface changes

Depends on the final decision.

API changes

(API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate.)

Data model changes

None.

Release notes snippet

None.

🌱 Plan

Status

Fixed

Version

2.0

Component

Code

Created by

🇮🇩Indonesia gausarts

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment 10 months ago →
🇺🇸United States hockey2112
I recently upgraded from Drupal 8 to D9 and then D10. Now, my blazy images are stretched horizontally in their colorbox, and I think it is due to this feature being removed. I added some CSS (below), but that causes some really awkward transitions when switching from image to image.

#cboxLoadedContent img[srcset], #cboxLoadedContent picture img { width: auto; }
How can I regain the functionality that this feature provided, or at least establish a more elegant way of controlling the image sizes on the front-end?

contrib.social Blog FAQ Discussions

Production build 0.69.0 2024