iOS7:
Chrome - :y: :y: (both good)
Safari - :y: :y: (both good)
Android:
Chrome - :n: :y: (image blurry)
Firefox - :y: ??? (canvas is crisp but no animation)
OSX:
Chrome - :n: :y: (image blurry)
Safari - :y: :y: (both good)
Opera - :y: :n: (canvas is broken https://dl.dropboxusercontent.com/u/1534394/osx_opera.jpg (http://))
Firefox current - :y: ??? (canvas is crisp but no animation, no errors in console)
Firefox old (3.6) - :y: :n: (don't think canvas is available, didn't think it was worth looking into. Shows unzoomed image)
Windows 7:
IE10 - :y: :n: (canvas blurry and not animated)
Chrome - :n: :y: (image blurry)
XP (lol):
IE8 - :y: :n: (JSfiddle doesn't actually manage to initialise, haha, but IE8 was pre-antialiasing and pre-canvas so... assumption).
Thank you! :'( I've waited so long.Yep, I ran into that one too. I haven't figured out yet why it's happening, but yes, your best bet is to turn it off for a sec :/
Actually, on some pages, such as the daily challenge thread pictures near the bottom of the page didn't load when I had this script on. When I turned the script off it loaded just fine. Is this happening for anyone else?
Works. You're a rockstar. :crazy:Heh, I've been trying to get this to work for a while now, because I knew it would be possible. I've been working on similar stuff for a while now and I suddenly gained the knowledge to tackle this :)
. . .
The next version will have these and I'm assuming it'll fix that elusive bug where the images stop rendering halfway down a thread.
Yep, this is a problem. My workaround is hitting a "Quote" link on a post on the page and then using the browser's Back button. Shouldn't make a difference, but it does - all images show up.The sporadity of the bug and the fact that it shows up more or less for certain users, combined with how it shows up, leads me to believe that it's a bug in the browser's rendering, possibly caused by either too many zoomable images or by setting up too many render loops.
The good news is that it works (the images are now loading all the way through a thread), Gil. Nicely done and thanks because it really is awesome.Ah yes, I'll have to remedy that happening. I'll set up a max size for the next version. For now, the easiest way is to turn the script off when looking at large images. It will only start to render when first clicked.
The bad news is that a friend just linked a 2818x4062 image to me and I clicked it once to make it native size, then once to make it small again, then again because I thought the click hadn't registered (where actually it was just slowly trying to render it) and then my PC crashed.
I'm thinking maybe you should set a max size, or switch off that feature if it's no longer needed (as I understand it, it's only there as a workaround for images not loading?).
I have a quad-core i5, a GTX 470, Windows 7 Pro SP1 and the latest Chrome, by the by.
The good news is that it works (the images are now loading all the way through a thread), Gil. Nicely done and thanks because it really is awesome.Ah yes, I'll have to remedy that happening. I'll set up a max size for the next version. For now, the easiest way is to turn the script off when looking at large images. It will only start to render when first clicked.
The bad news is that a friend just linked a 2818x4062 image to me and I clicked it once to make it native size, then once to make it small again, then again because I thought the click hadn't registered (where actually it was just slowly trying to render it) and then my PC crashed.
I'm thinking maybe you should set a max size, or switch off that feature if it's no longer needed (as I understand it, it's only there as a workaround for images not loading?).
I have a quad-core i5, a GTX 470, Windows 7 Pro SP1 and the latest Chrome, by the by.
Yes the script is now loading on every page. It should be restricted to wayofthepixel.The current script is not specific to Wayofthepixel, it's an all-around script. Changing it to only work on Wayofthepixel is easy though. I'm just not sure if I can make options for this. I'll look into it.
CSS's image-rendering: pixelated is supported in Chrome from 41.