Well that's nice. I asked if these bugs were going to be in AOL 8 though. How about this for a showstopper form bug though?
<form name="t"> <input type="hidden" name="foo"> <input type="Checkbox" onclick="document.t.foo.value = 'test'"> </form> Now reload the page. The checkbox stays, but the hidden value is cleared. This bug alone makes javascript unuseable on forms, AND Mozilla thinks this is the right way to do it. It's been filed for a long time and they see nothig wrong. jon Bamm Gabriana wrote: >>bugs, bugs, bugs...search for form on bugzilla. Try to develop a form >>that uses javascript extensively. Lot's of inconsistencies...then hit >>reload. bah. Honestly I do spend 90% of my work week developing >>forms of some kind. It's true. > > > Welcome to the club. Since most of us here are developers, then it > follows that most of what we do on the web also relates to forms. > > Please understand that making things work for Mozilla is not a > workaround. Mozilla implements Javascript, Html and Css in a way > that is most consistent with W3C standards. > > A paradigm shift: what you are doing to make things work in IE is > the workaround, since it is IE that is not standards compliant. > > Finally: Mozilla is not intended to be an end-user product. The > download page says it all: Binaries are made available for testing > purposes only. > > If you do find what you believe to be a legit bug, the proper thing > to do is to file a bug report, or fix it yourself by submitting a patch. > > >
