Clearing the cache removes the problem … how annoying … can’t expect customers to do that… it was FF 3.5.3
interestingly upgraded to FF 3.5.5 … it came back… cleared cache and ok again.
