Marquee component not loaded due to MIME error

Description

I have been using the marquee component for my site since 6 months ago, all goes well. Few days ago the component stops loading and it blocks the loading of the first page as well. I try to find the error by checking the console and here is what I found. Looks like the error comes from Finsweet side, which I can do nothing about. Could someone please help me look into it?

Site URL

Required: Please provide a staging/production URL where we can see the issue

Steps to Reproduce

If we load the site, you can see that the landing page is a blank.

Expected Behavior

I expect the marquee to be loaded as normal like before. The marquee in the picture below should appear.

Actual Behavior

The link of the marquee js returns a wrong file type so the whole marquee component does not work.

Video/Screenshots

Required: Please provide a short screen recording showing the issue

  • Screenshots (if applicable):

Additional Context

  • Browser: [e.g., Chrome 120, Safari 17]
  • Device: [e.g., Desktop, iPhone 14]

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

Hey @jasper.chang.chn!

The CORS error in your console is coming from canvas.webflow.com — that’s the Webflow Designer environment, and it’s completely expected behavior. The Marquee component needs JavaScript to run, and the Designer doesn’t execute external scripts in preview mode. Your published site is not broken because of that error, so no worries there.

The real issue is that you’ve got two scripts trying to handle the marquee at the same time:

  1. https://cdn.jsdelivr.net/npm/@finsweet/attributes-marquee@1/marquee.js — this is an old, legacy script that’s no longer part of the current Finsweet system
  2. finsweetcomponentsconfig-1.0.4.js — this is the correct, current Components config injected by the app

Your marquee already has the right fs-marquee-* attributes, and the Components config is already doing the work. That legacy script is likely causing the conflict and the MIME type error you’re seeing.

Here’s how to fix it:

  1. Open your Webflow project and go to Page Settings for the affected page, or Site Settings → Custom Code if it was added there
  2. Find the script tag containing attributes-marquee@1/marquee.js
  3. Delete that script tag entirely — no replacement needed, the Components config already handles the marquee
  4. Save and publish the site
  5. Test on your published .webflow.io URL, not in the Designer preview

Once that old script is removed, the marquee should load correctly since the Components system is already properly set up. :flexed_biceps:

If it’s still not showing after publishing, drop a follow-up here and we’ll dig deeper into the setup.

Description

I have been using the marquee component for my site since 6 months ago, all goes well. Few days ago the component stops loading and it blocks the loading of the first page as well. I try to find the error by checking the console and here is what I found. Looks like the error comes from Finsweet side, which I can do nothing about. Could someone please help me look into it?

Site URL

Required: Please provide a staging/production URL where we can see the issue

Steps to Reproduce

If we load the site, you can see that the landing page is a blank.

Expected Behavior

I expect the marquee to be loaded as normal like before. The marquee in the picture below should appear.

Actual Behavior

The link of the marquee js returns a wrong file type so the whole marquee component does not work.

Video/Screenshots

Required: Please provide a short screen recording showing the issue

  • Screenshots (if applicable):

Additional Context

  • Browser: [e.g., Chrome 120, Safari 17]
  • Device: [e.g., Desktop, iPhone 14]

NDA Notice: If you’re under an NDA, please feel free to send us a Direct Message/Email with the above information.

Hello, thanks for your help. I went to site settings and was able to found the script you mentioned, and checked all other places for custom code to ensure there is no other places this script is still in. After saving and publish the issue is still there. But from the console in browser, there is no the MIME error anymore.

Can you check the published webflow.io URL to look into it further?

Thank you very much.

Hey @jasper.chang.chn

We’re looking into this

Hey @jasper.chang.chn

The issue should now be resolved, please check & confirm

Make sure to clear cache or load site in incognito while checking it out

Thanks