This thread has been a bit of deja vu for me. I have been discussing this problem with an external developer who uses Satay, who doesn't seem to believe that it is flaky. He has tested it across many browsers/OS's and hasn't seen the problem, and therefore had difficulty believing there is a prob. If you want to use the Satay method, and you've thoroughly tested it, and it works perfectly everywhere, then go for it, but I will maintain that it IS a buggy method, and some of your users will experience the "blank text box" syndrome, whether you as a developer have seen it or not. Ben.
> Reiterating Ben's comments and Zeldman's summary of the > problems with the > Satay method in Designing With Web Standards, that's exactly > the problem > with the Satay--sometimes it works and sometimes it doesn't. On some > browsers, on some machines, sometimes. I think Zeldman's > comment is how many > people do you want to choose to alienate? ********************************************************************** This message is intended for the addressee named and may contain privileged information or confidential information or both. If you are not the intended recipient please delete it and notify the sender. ********************************************************************** ****************************************************** The discussion list for http://webstandardsgroup.org/ Proud presenters of Web Essentials 04 http://we04.com/ Web standards, accessibility, inspiration, knowledge To be held in Sydney, September 30 and October 1, 2004 See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
