Question

In IE I am able to have data entered via a fields on a html form carry through to the Twiki form appended to the topic page generated via the html form.

However in Firefox data selected via the drop down list boxes does not carry through to the appended TWiki form on the topic page. The data entered in text fields IS carried through. It is only possible (once you are at the relevant topic page), using Firefox, to select the relevant values from the drop down list boxes on the form on the generated topic page. Hope this makes sense.

Does anyone have any clues about this differing browser response.

Environment

-- SueLocke - 21 Nov 2004

Further information

Just been on the Firefox site to see if this has been reported previously. Doesn't seem to be. I've now downloaded Mozilla to see if the problem occurs there. Yes it does, so it looks like a Mozilla issue rather than a Firefox per se. I found a similar bug report there - https://bugzilla.mozilla.org/show_bug.cgi?id=259792 - but its not exactly the same issue - more a related issue, with the bug seeming to have lain dormant for a few months.

-- SueLocke - 22 Nov 2004

Answer

I use Firefox all the time on TWiki.org and haven't had this problem, so it may be specific to your form - does it also happen on forms at TWiki.org or forms generated by TWiki WebForms on your site?

You might want to get some of the Firefox developer tools to spy on what's actually sent over the wire - also, try disabling all extensions in case they are causing the problem.

-- RichardDonkin - 24 Nov 2004

I thik yoour problem is non-conforming HTML which is being interperted by the two browsers in dffernt ways.

Do you realise you have...

   <FORM ....
   <H2> title ....
    ... table stuff ...
    ... rest of form stuff ...
   </FORM>

I'd start by taking that header out of there. Its not necessary. While I can't find anything in my reference books to say its not permitted, it may be one of these things that different rowsers handle in different ways and hence produce side-effects.

The other thing I'd look at is that you are using

<option value>Aging</option> 

My refence books say you should use

<option>Aging</option> 

<option value="Aging">Aging</option> 

I prefer the first format.

Finally, my references say that the end tag must be </select> and must never be ommited. You simply have </> if I'm reading things right.

This seems to be a case of browsers being liberal about non conforming HTML in differnt ways.

You might try taking the resulting HTML page, saving it, and running HTLP-tidy on it and see what it complains about.

-- AntonAylward - 27 Nov 2004

Thanks Anton for spending the time and having a look at the code so thoroughly. I'll work it through. Your comment This seems to be a case of browsers being liberal about non conforming HTML in differnt ways is a good pointer. I've been picking this up as an issue between IE and Firefox - and must make a note to myself - develop in Firefox - have just come over to Firefox and old working habits die hard

-- SueLocke - 27 Nov 2004

Anton - just edited the form to remove the value syntax and close off the select. Works great. Thanks again

-- SueLocke - 27 Nov 2004

"When all else fails, read the documentation" ... that and "It works better if you plug it in" have always been standfast maxims for me.

See my comments in mnay other places about the ideosyncracies of browsers and hwo they handle non-conforming HTML.

       ____ ___ ____ _   _      
__/\__/ ___|_ _/ ___| | | |_/\__
\    /\___ \| | |  _| |_| \    /
/_  _\ ___) | | |_| |  _  /_  _\
  \/  |____/___\____|_| |_| \/ 

-- AntonAylward - 28 Nov 2004