Forum Moderators: not2easy

Message Too Old, No Replies

Netscape and form values

Puts the form value anywhere it pleases?

         

MatthewHSE

12:39 am on Aug 10, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I've got a page with a couple one-line forms on it: one for searching and one for joining our e-list. I've assigned descriptive values to the text fields in both those forms, but Netscape 6.1 is slapping the text for that value anywhere it likes around the page. For instance, it will leave the form field where it belongs, but moves value text 200 pixels above the field. Is there any way around that?

It's not only annoying; it's downright confusing. Not only does text get placed over graphics, out of context, etc., but clicking in the form field places the cursor wherever the form field value has been arbitrarily placed on the page.

Purple Martin

1:04 am on Aug 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Apologies for not answering your question but:

There are very few people with Netscape 6.1, it's almost non-existant. It was only available for a very short time between 6.0 and 6.2, so the number of downloads was tiny. If your page looks OK in 6.2 then maybe you should just ignore the problem.

pageoneresults

2:46 am on Aug 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



You may also want to validate that page to make sure there are no blatant nesting errors. Some browsers are just more forgiving than others.

MatthewHSE

1:14 pm on Aug 11, 2003 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Thanks guys; turns out I had forgotten to set the height for a table cell above the forms and it seems that Netscape was just rendering the form value at the height it would have been if that table cell had no height at all. When a picture loaded in the table cell and forced it to take some height, the form got moved down but the value, for some reason, stayed where it was.

I set a height value for that cell and now the problem is fixed.

Thanks for answering though!

Matthew