Skip to content
This repository has been archived by the owner on Feb 23, 2023. It is now read-only.

Anonymizer issue #1747

Closed
mcnesium opened this issue Nov 29, 2017 · 3 comments
Closed

Anonymizer issue #1747

mcnesium opened this issue Nov 29, 2017 · 3 comments

Comments

@mcnesium
Copy link

Sorry for opening a new issue, but I can't reopen #1113, maybe you can merge.

I did some research: the old fancybox page runs v2.1.7 and when I edit one of the image links and add https://nullrefer.com/?http… to the href attribute in the devtools, this error message appears:

The requested content can not be loaded. Please try again later

But on the new fancybox page this does not happen. Instead, the expected image pops up.

Why is that? Whats the difference? I checked this in both Firefox 57 and Chromium 62

Maybe you can give some advice over here

@fancyapps
Copy link
Owner

fancyapps commented Nov 29, 2017

Hi,

Nothing has changed, it is still not working.

Look, you can open images directly in the browser by prepending https://nullrefer.com/? to the link, for example: https://nullrefer.com/?https://developer.mozilla.org/static/img/mdn-logo-sm.png

But it just does not work for html, for example, try:

<img src="https://nullrefer.com/?https://developer.mozilla.org/static/img/mdn-logo-sm.png" />

Demo - https://codepen.io/anon/pen/ooaKvx

If you could make it somehow work for images, then fancyBox would work, too.

@mcnesium
Copy link
Author

mcnesium commented Nov 29, 2017

You're right, it still does not. This must have been some caching thing over here, that made me think it does. Sorry about the noise.

@jtojnar
Copy link

jtojnar commented Nov 29, 2017

Changing the href is not enough to break it because the new demo page also uses srcset. If you change it there it will break too.

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants