Browser, not engine. As with bug 61385, over to Security component -
Assignee: rogerl → mstoltz
QA Contact: pschwartau → ckritzer
Yes, I can reproduce this with build 2001010204 on Win98. No posting occurs until workarounds described in the testcase are applied EXCEPT that workaround 3. does no longer work (3. renaming image used in INPUT, so that it can not load) - has no affect now. BTW I also noticed different browser behavior when testing posting offline (when there's no response from server): previous versions stopped "redrawing" the targeted frame; above mentioned build freezes. By "redrawing" I mean the possibility to select text with mouse.
Marking NEW as per comments.
Status: UNCONFIRMED → NEW
Ever confirmed: true
This appears to be related to bug 61385, reassigning to rpotts, who owns that one. Please reassign if I'm wrong.
Assignee: mstoltz → rpotts
Component: Security: General → Form Submission
I no longer think this one is related with bug 61385 because that one has problem with termination of one "loading" with the second "loading". And that is not the case here. This one simply does not send the form! And is somehow related to the input being of type image. For expalmple input with type button works correct. So it has nothing to do with bug 61385 !
I'm really sorry for the time wasted on this! This is NOT A BUG! I made more thorough research on this and found this: The input of type image surrounded by form element with no properties takes default action; it send the form with "get" method with the x y coordinates of the point clicked in the image. And does not perform the onClick action. That's why it did not change the second frame. And removing the empty form element is the solution for this. Than it behaves as desired (does the onClick). So please change the status of this bug accordindly. Once again sorry.
Not a bug. Reasons in the sprevious comment.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → INVALID
No problem, thanks for investigating this yourself! VERIFIED invalid.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.