Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plugin blocks images from CDN for Instagram widget #402

Open
blacksaildivision opened this issue May 24, 2019 · 5 comments
Open

Plugin blocks images from CDN for Instagram widget #402

blacksaildivision opened this issue May 24, 2019 · 5 comments
Labels
as-expected The addon is intended to work this way or break this flow

Comments

@blacksaildivision
Copy link

  • Facebook Container Version: 1.9.0
  • Operating System + Version: Microsoft Windows 10 Pro 10.0.17763
  • Firefox Version: 67.0
  • Other installed Add-ons + Version + Enabled/Disabled-Status:
    Facebook Container 1.9.0 true @contain-facebook
    Adobe Acrobat 18.0.10 false [email protected]

Actual behavior

Plugin blocks images loaded from Instagram CDN in LightWidget widget. Widget is iframe based and it only reference to Instagram CDN is inside <img src="..." and srcset="..." attributes.

Expected behavior

The images should load since the Instagram website is added by default and images are loading fine when visited directly from the URL

Steps to reproduce

  1. Visit example widget: https://lightwidget.com/widgets/cb2a2d4dc812493dc6f46fe704041c8ede5cbf1b.html or https://cdn.lightwidget.com/widgets/cb2a2d4dc812493dc6f46fe704041c8ede5cbf1b.html the images will not load
  2. Check the page code and copy any of the images from src or srcset attribute and try to visit the image URL, it will load just fine
  3. Disable Facebook Container plugin and the widget images will load without any issues.

Notes

Not sure if this is expected behavior or not but would be great if the images wouldn't be blocked by default. There are lot of users using this widget:)

@maxxcrawford
Copy link
Collaborator

This is as intended for right now. We're adding the ability to toggle off/on site support in the next release that should resolve this.

@erictompkins
Copy link

The problem with the Facebook Container blocking Facebook videos as mentioned in #438 is that absolutely no information is shown on the page to indicate why the video isn't showing. Our clients are complaining that their videos aren't showing on their websites because Firefox doesn't provide any information where the video would be that it blocked the video.

If you are going to block videos by default then Firefox should show some sort of message in place of the blocked content on why it was blocked and how to unblock it. This is a bad experience for people who are expecting to see embedded videos on pages.

@maxxcrawford
Copy link
Collaborator

@erictompkins Eric – Sorry to hear that. For clarification, are you describing an issue with Firefox behavior? Please note that this repo only applies to the Facebook Container add-on.

@erictompkins
Copy link

@maxxcrawford Yes, I'm referring to an issue with Firefox behavior.
Go to https://www.emmanuelassembly.com/. There are a number of Facebook videos on that page (everywhere you see "Video loading..."). The Facebook Container add-on is blocking all videos. See the screenshot.

image

I understand that the add-on is blocking the videos because of tracking that Facebook includes in all of it's embed code. Most people probably don't realize that Firefox is doing this and since Firefox provides no adequate visual indication that the video was blocked, people think that the website is broken. This is not a very good end-user experience.

The only visual indication is a small icon in the upper right (the gate icon) with a small purple dot on it. Most people won't notice that or even know what that means if they do.

Please add support for showing some sort of message in context of blocked content on how to not block it. In the current form we're having to put in our own messaging to try and explain why the video doesn't show, which is far from ideal.

image

If you need any more information please let me know.

@NormG1
Copy link

NormG1 commented Aug 2, 2021

This is as intended for right now. We're adding the ability to toggle off/on site support in the next release that should resolve this.

It has been two years since you indicated your intention to fix this. I want to see webpages as the creator envisioned them, and many webpages use images from Instagram the way one might use stock photos or even as a repository for the creator's own images.|

I prefer not to see a link to open a separate webpage to see the image. Imagine buying a magazine like National Geographic, and inside the magazine where the photos should be, is just some text, telling the reader to go back to the newsstand and pickup the free companion magazine called National Geographic Images, where I can go look to find the images the author chose to illustrate their text.

If you haven't fixed this in two years, I'm assuming you will never fix it. Facebook owns Instagram, and the applications are more tightly tied together than ever. I'm not a programmer and don't claim to understand what Containers even do or why I should want to use them. Or the challenges you as the developer of Facebook Container face in making what you do less obvious in the typical user experience. Maybe it isn't even possible, which is why this issue has been tagged as AS-EXPECTED and all similar issues merged and closed.

I just disabled this Extension and Firefox works as expected. If this means Facebook can track my activity across websites, well, so be it. If the price I have to pay to use Facebook containers is to see a link to an image instead of the image itself. I guess this extension has to go.

Ublock origin does a fantastic job of keeping most intrusive ads out of Firefox without making my webpages look like swiss cheese. I cannot even tell uBlock is working. It just is not obvious in my daily experience until I use a public computer and see all the garbage uBlock is blocking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
as-expected The addon is intended to work this way or break this flow
Projects
None yet
Development

No branches or pull requests

4 participants