Thanks, that's good info. I was thinking along the lines of adding a small menu somewhere that would allow you to manually choose the size and override whatever resolution is reported. But it's been a long time since I dabbled in web design, so that'll be a great place to start. :-)

If there has to be a minimum resolution set server-side, I agree that it should be adjustable. But I think it would be far more useful to adjust it client-side, to be as flexible for different viewer sizes as possible. I wonder, if it's just a matter of a value the browser is reporting, a quick-and-dirty addition might be doable with some basic PHP/CSS. Tom, any thoughts on that?

Yes, that could have been why I saw the performance hit. I thought my initial scan was finished at the time, but I could be wrong.

Yes, I'm using 1.5.0. Thanks for checking on it.

Oh, I didn't realize the standard browser wasn't available. It's still on my tablets as well as my S4. No problem, I'll just use Chrome instead; just wanted to point it out.

Thanks for all your efforts! I've been enjoying the software immensely despite any bugs.

Just tried opening a comic on my tablet in the default Android browser*, and got the same results as with FF. Image width is definitely not being limited. With the tablet in landscape (width of 2048), the width was fit to the screen. In portrait mode (1536, I think), I had to scroll horizontally. Chrome for Android also didn't hit the 1200px bug, but it did shrink to fit the screen width in both landscape and portrait. Does this bug only come up in certain situations?

I can post screenshots if you'd like to see anything.

* The default browser also has some issues with button placement on the Download/Read screen. It seems that the click regions are centered as they should be, but the pop-up menu is not. Not sure if that's something you can fix in layout or just a problem with the browser. Chrome didn't have that problem and displayed it just like the desktop version of Chrome.

That's understandable; it's always a good move to keep the interface relatively simple. I feel like "Advanced" tabs are always allowed to be more complex, though. ;-)

About the preloading: I think the first time I used the comic reader remotely (i.e., from outside my home LAN), I must have been experiencing some other performance issues. When I tried it again yesterday, flipping through a comic with very large images was quite fast and pleasant. So I have no problem there after all; very well done!

The resizing is not something I've noticed. In a maximized Firefox window (GNOME 2 on RHEL6) on a 1680x1050 screen, images were still taking up the entire width of the window. I'll check it out on my tablet later (generic Android with a Retina display) and see what happens there.

In any case, I think the fit options and the upcoming advanced settings sound like exactly what I'm looking for. I'll be looking forward to seeing those. Thanks for all of your time and effort, and keep up the great work!

Hi! First of all, great application. I'm pleased to see that you intend to focus on perfecting the content delivery system rather than adding a bunch of unnecessary features. The comics reader is the best and simplest such utility that I've found.

Question regarding this particular feature: Do your plans for improving the comics reader include server-side image resizing, or is the "fit" function done by the client? I think the former would be a great way to improve loading speeds. If the admin panel had the option to specify a maximum size to send to the client, and could resize and cache the images in advance, it could result in a lot less data transferred and a much quicker, smoother experience.

Also, it would be really slick if a few pages could be preloaded to the client; two or three pages would be enough to eliminate the waiting for page loads entirely.