Wrong srcset in responsive image

Created on 4 January 2024, 5 months ago
Updated 18 January 2024, 5 months ago

Problem/Motivation

The responsive image is causing a JavaScript error
GET about:blank net::ERR_UNKNOWN_URL_SCHEME

Steps to reproduce

  1. Enable the Support Responsive image feature
  2. Do not enable any No Javascript options

I also attached my blazy settings.

💬 Support request
Status

Fixed

Version

2.22

Component

Miscellaneous

Created by

🇻🇳Vietnam linhnm

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @linhnm
  • Status changed to Fixed 5 months ago
  • 🇮🇩Indonesia gausarts

    Thank you.

    You are correct.

    Let's understand the fundamentals:

    1. Uninstall Responsive image, and Blazy will be just fine without it. Meaning, it is a nice feature to have, not a dependency that will screw Blazy up if not installed. Any issue or error with such a non-obligatory feature is never a bug. It is just a support, feature, or lacking of it.
    2. What you did is called rare DEV behaviors -- by-passing both Blazy and browsers' behaviors. Not normal users'. Any issue or error caused by such a bypass is your own unique DEV errors. Proof? Press F5. Close that Console. Avoid Inspect element button early. Scroll from top to bottom, or vice versa, and allow Blazy and browsers do their jobs. Re-open the console, F12. Do you still see errors?
    3. There was a reported issue that leaving srcset empty had caused invalid value errors with HTML validators. The value about:blank is the only second valid value without causing extra HTTP requests, nor double downloads. That is why it is there. If it caused errors identified in #2 above, it is beyond this module. It is your own unique behaviors who by-passed the browsers' and Blazy mechanisms.

    There can be few other if not similar errors when things are by-passed.

    Feel free to re-open, should you have a better solution that addresses all the above correctly.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.69.0 2024