Member
2010-04-13, 02:35 PM
Just to note that I've switched back to v. 5.1.01 and still have the same problem. Since I didn't mention it in my OP, the problem does NOT occur on Firefox, Safari or Google Chrome, only on OmniWeb. So it's back in your court.