I try to check out all the updates for Neptune just to see how they look/work, and see if I would want to include some new feature in my albums. When I try the slide arrows off-image I see no change. I have checked the layout/slide option, cleared cache, and refreshed the test album loading, but the arrows are still on-image. What am I missing?
Yeah, unacceptable in Chrome. Please reinstall Neptune 24. I'll come back to this one, but since it was a CSS kludge, rather than a true modification to the Floatbox script, I don't have much hope of getting it to behave.
Thanks for looking into it, knowing that 99% of the time the problem is me. To add more info, Firefox is my default browser, so I was/am using Firefox. I have attached a screen shot on the settings page, and a shot of the results page. I did a "remake all" just to be sure the album was regenerated, and I did the F5 refresh after displaying. I tried it with both Neptune and Saturn and got the same problem. I haven't tried it in other browsers.
Mystery solved. It's because of some of the custom CSS in your albums, the stuff you always include. There's one line of that in particular that would undo this change. It was colliding with the CSS changes for the off-image nav arrows.
Most of that is unnecessary. the position, background-color, and padding are the default values, so there's no need to specify them again. But two of those are precisely the things that this modification needed to change (to a fixed position, and no background). The opacity change is OK.
Now wait a minute - I'll take partial blame, but surely I can push some of the blame off onto the developer for allowing a user's legitimate UI CSS mod to conflict with his desire to kludge the program just to satisfy his desire for some weird feature that almost no one will use
I kind of liked the option. It's more common to see prev/next arrows on the edges of the viewport, rather than appearing on the image itself. Here's a little demo so you can see what it's supposed to look like.
I deleted all of the entries in the string except the opacity, and the album behaved as you expected. If the majority of the photos in an album are landscape (and particularly 16:9), as are the first few in your sample album, the slide arrows on the view port edge make sense. But when the photos are portrait (as in the attached) the slide arrows are almost unnoticeable. I'll spot you that if viewing an album that starts with a wide landscape photo the viewer would tend to keep the cursor on the view port edge, so even the portrait photos would probably not be a distraction. Just a matter of preference and getting used to seeing the arrows on- or off-image.
I'll spot you that if viewing an album that starts with a wide landscape photo the viewer would tend to keep the cursor on the view port edge....
That's the plus side of stashing the arrow over there. A visitor can just mouse on it and keep clicking in the same place. Of course, one can do the same thing by planting the mouse to the right of the center line of the image and keep clicking. I had just noticed that on a lot of lightbox pages, the nav arrows were positioned like that, and thought I might offer that option.
The Chrome misbehavior might be limited to local preview when using the jAlbum built-in web server, but I'll have to do more experimenting to see....
I'm always trying to keep things from interfering with the display of the images. In other skins, I'm often bothered by things like a control bar that ends up being superimposed on the image.
(On a related note, I absolutely hate the popup status bars in virtually all browsers when you hover on a link - it's like an annoying jack-in-the-box.)
I was in the process of writing another note when I saw your latest. When I looked again at my album with the arrows on the edges it dawned on me that clicking the right/left image sides still did the advance/return that I preferred, so the arrows on the edges was not a distraction for me. In fact, having the arrows on the sides so they don't block any of the image has its advantages. Maybe the developer knew what he was doing all along.
Slightly modified, to cure the MS Edge problem. And I think David has cured the Chrome preview issue.
Your custom CSS should be fine, as long as you restrict it to the opacity setting change. Stay away from position, background-color, and padding - those will clash with the off-image nav arrows. And they're not needed for your albums, anyway, regardless of where you put the nav arrows.