It works for me on the desktop with both. Can you complain to tapatalk? Their support forum is here: https://www.tapatalk.com/groups/tapatalksupport/
Images not loading in Chrome
- stonehillnews
- Posts: 83
- Joined: Thu Dec 15, 2016 1:31 pm
Potentially due to the fact they are hosted externally and maybe your ad blocker zapped them.Sean wrote:Thanks for the report! BTW - the images wouldn't load for me in Chrome mobile app. Had to use Firefox.
Oh, it's 100% because they're hosted externally. But that doesn't mean things shouldn't work, just that tapatalk doesn't test their thing. Which we already knew.stonehillnews wrote: ↑Potentially due to the fact they are hosted externally and maybe your ad blocker zapped them.
Sean: what happens if you click on one of the images that didn't load? It SHOULD load the original full-size image from my server. Do you see the image? And if not, does the location the browser thinks it's looking at change?
Thanks for the suggestion. Allowing popups and ads did not fix it though. I guess I'll complain to Tapatalk when I have nothing better to do.stonehillnews wrote: ↑ Potentially due to the fact they are hosted externally and maybe your ad blocker zapped them.
Yeah, it can't be anything else. All posts are written using phpbb, and I write all my posts to show the low-res image and to directly link to the full-res image if somebody clicks. Browsers don't speak phpbb, and tapatalk is doing the translation from phpbb to html, which browsers do understand. I guess on mobile chrome that translation is broken for the displayed image, but at least the link works. They could have broken that part too.
Rico: if you have a moment, please report the issue on tapatalk's support forum. I can do that myself, but since I don't experience this issue myself, I can't answer any follow-up questions they may have.
This may or may not be related. Right-click on the broken image, and "Copy link location" or "Copy link address" or whatever. That address is the image it's trying to load. If you past that address into your web browser you'll see that the address you're using isn't the address of the image. Use the correct address next time