Custom Query (1173 matches)
Results (166 - 168 of 1173)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#208 | FIXED | If there are no next and previous media, the navigation buttons should not appear | ||
Description |
Speaks for itself. If you only have one piece of media for whatever reason, the navigation still shows up. But both of the buttons are disabled, so they may just as well be gone completely. I have no idea how hard this is to do though. Attached is a screenshot. |
|||
#209 | FIXED | Make next / previous universally non-confusing (possibly with thumbs?) | ||
Description |
Right now we have next/previous buttons like: [] The problem: it's confusing. I made a suggestion on how to fix this once, by reversing the order of the arrows: `http://bugs.foocorp.net/issues/423 <http://bugs.foocorp.net/issues/423>`_ However I'm not sure this really makes things clearer. Either ordering is confusing here: - [] is what we used to do but this is confusing because our galleries go in the opposite direction (newer on left, older on right), which is what makes sense for a gallery to be like. - [] is what we do now, but that's also totally confusing. Who really expects arrows to point this way? Not me (even despite filing that old ticket). Imagine reading a webcomic ordered this way. That would be crazy! So here's some suggested resolutions: - Switch back to the old behavior and add text to the arrows, like [] - Add smaller-thumbnail support (75-100px?) and make these thumbnails the navigation. I'd opt for `#1 </issues/1>`_... maybe we can make #2 a different ticket and add an ajaxy "quick browser" like flickr has that's scrollable left and right, and make that **separate** from the current next/previous arrow buttons. Bonus point: doing `#1 </issues/1>`_ will fill up some of that glaring whitespace on those current buttons ;) Dropping this in Jef's lap! Jef, what do you think? |
|||
#210 | FIXED | Favicon | ||
Description |
We could really use a mediagoblin favicon! Not all instances have to use it, but it'd be nice to have in. |
Note:
See TracQuery
for help on using queries.