On 20050425 1049, Jim Brown wrote: > Now set to size=50. Please check and let me know.
That seems to have solved the problem. Thanks for the quick response. As it happens, I don't even think it matters if the size is set to 1 or 1000; theoretically it can accept input of any length, and the browser can scroll. It just becomes a problem when the size is less than 1, at which point the field doesn't get rendered at all. I could experiment to find potential breaking points if I had time, but that may not happen. FYI, my main browser is W3M. - http://w3m.sourceforge.net/ - http://w3m.sourceforge.net/index.en.html When that broke, I checked again with Links - http://links.sourceforge.net/ and found the same result. Lynx, which everyone probably knows, seems to ignore possibly unreasonable settings. In any case, for any positive size, all of the above browsers can accept a greater amount of text, I'm fairly certain, so it may not be a critical detail as to exactly how big to make the field, as long as it is bigger than 0. For more background, I do random contract jobs in often low-budget *NIX labs that often have machines that can not run X, such as the machine I use now. Most people I know in these situations use either W3M or Links, given that they support pretty much all standard features one might find in a modern graphical browser (Links lacks a good deal of i18n support), although most people I talk to these days hasn't used any kind of text browser in years, if they ever did at all. In any case, I do believe that W3M and Links make good additions to any list of browsers when testing web pages for compatibility. Anyway, thanks for your concern. I'm going to fill out the survey soon. I didn't submit anything yesterday for lack of time after playing with HTML code. Regards, Dan Bernard _______________________________________________ BSDCert mailing list [email protected] http://lists.nycbug.org/mailman/listinfo/bsdcert
