Topic: New design not work on old devices

Posted under Site Bug Reports & Feature Requests

This topic has been locked.

New design not work properly on old devices such as iPad 4 iOS 7.0.4. The interface works at 50% and not display any images. Also can't enter to advanced settings. It would be great to have switch to old design, if it possible.

Tested on Safari, Google Chrome.

Updated by KiraNoot

I'm going to be assuming it uses some Google-specific features or Canvas or something. :(

softscale~ said:
IOS 7, which hasn't been officially supported since 2014? Are you serious?

Some people don't buy phones every year.

Yeah, deleting other post. I guess this belongs here.
Subject: Images not loading
"Suddenly, no image thumbnails show up in search results. Tried other tags and not working. Is it ISP issue or did something change in the last couple of hours on the server?"

See if you can provide some screen shots or videos of the interface issues. Examples from Sea Monkey:
https://a.uguu.se/hdYA2XpgX1iB_e621exampleofimagesnotshowingup.png Pool empty
https://a.uguu.se/IeUkZhB14arl_e621exampleofimagesnotshowingup2.PNG Image not showing

Note that "Uguu lets you store file(s) up to 100MB for 24 hours." so these will disappear tomorrow.

Updated

I have the same problem, images are not loading at all on the older device.
Y'know, the "if ain't broke don't fix it" saying doesn't exist for no reason.

Sort of a fix, if your browser has an inspector (or adblocker that lets you create filters for styles).

Delete this node in the Inspector (debugging tool that you press CTRL-I or Shift-Control-I for in some browsers - I think they all allow right-clicking with it on context menu).

<style id="blacklisted-hider">
    .post-preview, #image-container, #c-comments .post, .mod-queue-preview.post-preview, .post-thumbnail {
      display: none !important;
    }
  </style>

I think I'll write a filter for uBlock Origin for now, to change it from 'disply: none', but this is apparently a bug triggered by not using a browser in most unrestricted settings. I tried disabling uBO, and so on, and found out it was this line. Apparently, blacklists work by just making the post's thumbnail invisible, not preventing it from being found in the first place (server-side versus client-side?). I guess this is just the wrinkles of the new site's engine. I'll try to find exact and useful/repeatable steps for any other bugs I see. Thanks admins for putting up with our gripes on a free site! :-D

I suspect very much that this effectively nukes blacklists, Tl;Dr version.

"e621.net@##.post-thumbnail:style(display: default !important;)" Am I doing that right in uBlock Origin custom filter? I think that's how style filters work on it. Note that "display: inline" should be the default value for CSS in a modern browser. <-- Actually, 'default'?

My intent was changing:

<style id="blacklisted-hider"> .post-preview, #image-container, #c-comments .post, .mod-queue-preview.post-preview, .post-thumbnail {display: none !important; } </style>

To:

<style id="blacklisted-hider"> .post-preview, #image-container, #c-comments .post, .mod-queue-preview.post-preview, .post-thumbnail {display: default !important; } </style>

I've not really made any style filters for uBlock Origin, so need some help figuring this out. Guess I'll look at existing filters and use a search engine to find explanations. If I change that manually, it works. Also, I looked into old code and saw something entirely different, which is not really a surprise (obviously).

Updated

I'm having this problem too, seems that I can use everthing on the site but can't see any of the images. :(

I'm on an iPad and I use Safari

I found a temporary solution - use Puffin instead of Chrome or Safari. It's kind of more laggy, but work for now, even for flash and webm. But not sure about that for new e621.

Welp, trying to set that with custom CSS doesn't work. It loads the CSS file, but it does nothing. I have no idea how to fix it using that trick so it can work on all devices. Oh well... Blocking the JS file is brute-force method and not available to all browsers on all devices.

  • 1