Bug fixes - February 18th, 2006
Have some quick bug fixes out on the site today:
- lightBox was breaking some old versions of Gecko-based browsers (Netscape, Mozilla, Camino, Firefox).
- adding to the cart was also broken on those old browsers.
- removing all keywords in some cases wouldn’t show the ‘add keywords’ link.
- smugloupe on the Mac would resize funny when zooming in or out.
- Very long comments in IE would wrap poorly.
- Updated a help section to have the right CSS tag for photo keywords.
- When in single image view, hitting the next/previous links would sometimes crash IE.
- Right-click wasn’t consistently working with lightBox.
- Some country-specific TLDs still weren’t working right. (If you’re still having trouble, clear ALL your cookies and try again. Probably got a bad one - sorry!)
- Slick new stars for ratings & comments
- Put back the nice looking cogs for adding to the cart. We’ll see if we can somehow find a middle ground between ‘nice’ and ‘fast’, but for now, we’ll stick with ‘nice’
Hope that helps make someone’s weekend a little nicer.
February 20th, 2006 at 12:33 pm
Thanks for being committed to fixing things. Your level of customer care keeps me happy.
February 22nd, 2006 at 10:44 pm
I just started using your site and really like the features and unlimited space capabilities. Can’t wait to fill some disks. I have an issue with the filmstrip feature. The left and right arrows go in the opposite direction than what is normal. For me, and what seems natural, is if the stip is already automatically scrolling right, the user is looking towards the right, and pushing on that right arrow should get the user further in that direction. Currently it moves in the opposite direction which doesn’t seem natual. I would like a feature to either let the user pick what they want the arrow to do, or just reverse it.
This is a synptom of what I call the “Scroll Bar” problem, where basically you hit a scroll bar and don’t know ahead of time which will move, either the page relative to your view, or the view relative to the page. So either up or down in a document. Thus you are hacking and cannot predict the behavior until you click the button the first time:-) This also relates to how you draw datastructure stacks, either up or down.
Thanks,