- Issue created by @chambers
- Status changed to Postponed: needs info
almost 2 years ago 12:21am 22 March 2023 - 🇮🇩Indonesia gausarts
Thank you.
I haven't got time to see to it, but would like to clarify a few things first.
Removed settings:
- Custom
Breakpoints
were deprecated for core Responsive Image since 2-3 years ago. - Non-UI settings (those not visible as options: grid_header, _uri, etc.) were cleaned out as parts of the optimization last year.
- Options with empty values (lazy, and everything else) are never displayed at formatter summary to declutter since Blazy was created with formatters.
- Not sure, yet, but
current_view_mode
was never displayed as an option, so it was likely removed like the rest, too. Instead, checked programmatically somewhere, IIRC. What is always displayed isView mode
option. The first indicates the current formatter view mode, mostly used to provide CSS classes, the latter your chosen view mode of the selected entity (media, paragraphs, etc.), used to display its fields.
Boolean values (Background, etc.) had a value 0/1 which was replaced by no/yes for human didplay. When 0, it is never displayed as mentioned above.
Leaving the reported bugs to address: Background is no longer working. Is this what it is all about? If anything else, please detail more.
- Custom
- 🇮🇩Indonesia gausarts
I just checked BG and Loading priority are fine. Your issue is likely just confusion with the deprecated stuffs. Some were explained above. Do not compare those configs, in case confusing with the latest changes, see the frontend output.
> The media--background class has been removed from the background image and replaced with media--image.
Themedia--background
was replaced by theb-bg
class to accommodate non-media like form items, mostly seen at Slick Browser, including body with BG, etc. If you use it on your custom code, place update it. When BG works, you will see DIV tag, not IMG. The relevant classes were explained above.The
media--background
was no longer used since the initial full release 8.x-2.0:
https://git.drupalcode.org/project/blazy/-/blob/8.x-2.0/css/blazy.css#L29It did exist till pre-release 8.x-2.0-rc7 in tandem with
b-bg
:
https://git.drupalcode.org/project/blazy/-/blob/8.x-2.0-rc7/css/componen...The combo was prepared and existed since initial rc1:
https://git.drupalcode.org/project/blazy/-/blob/8.x-2.0-rc1/src/BlazyMan...And they were years ago :)
Changing
Loading priority
fromlazy
to anything else works as expected.I see no OP bugs with the latest, unless those deprecated mentioned were still used in your custom codes. In that case, please update it accordingly.
Let me know if anything else? Be sure to cooy/paste the BG element (b-bg) for investigation.
- 🇺🇸United States chambers
Thanks for all that. This site was created years ago so that explains everything you said. The image blazy settings probably haven't been updated since then. With those class name changes, I'll have to go through and update the class names in the style sheets. Thats where the front end starts breaking because it is looking for the media--background class name.
- Status changed to Fixed
almost 2 years ago 4:17pm 24 March 2023 - 🇮🇩Indonesia gausarts
Thanks for the follow-up.
Added a CR like the rest of RC changes, not many hopefully:
https://www.drupal.org/node/3103018#css-changes → Automatically closed - issue fixed for 2 weeks with no activity.