Closed
Bug 277295
Opened 21 years ago
Closed 20 years ago
Form elements don't get sent
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: mhauptma73, Unassigned)
Details
Attachments
(1 file)
|
305 bytes,
text/html
|
Details |
I update several form elements via javascript using innerHTML. It works perfect,
but it is impossible to access them via document.frmName.elementName nor do they
get sent to the server upon submit.
It works ok in IE but maybe I'm just doing something wrong :-(
If more data is needed don't hesitate to contact me.
Comment 1•21 years ago
|
||
Yes, I'd guess quite a bit more information is needed: ideally, a testcase that
shows the problem with as little HTML and JavaScript as possible, added as an
attachment, or a link to an example of the problem.
Assignee: bugs → form-submission
Component: JavaScript Console → HTML: Form Submission
Product: Firefox → Core
QA Contact: firefox.js-console → ian
Version: 1.0 Branch → Trunk
Testcase is problematic as the page makes use of database... If you give me an
email-address I can send you the URl and access-data.
Miguel
Comment 3•21 years ago
|
||
Comment 4•21 years ago
|
||
Ah, now I see the problem, which I'm guessing is Parser's problem if it chooses
to deal with it. The simplified version of the page is
<table><form><tr><td><font><select> where the <select> is added as innerHTML of
the <font>. First pass through, the parser fixes up that utterly misplaced
<form>, and adds form controls to it, even though they aren't children of it in
the DOM, but when another one is added as innerHTML, it doesn't get added to the
form's list of controls.
Assignee: form-submission → parser
Component: HTML: Form Submission → HTML: Parser
QA Contact: ian → mrbkap
Placing the form element outside the table solved the issue.
Thanks to Phil for helping with that issue.
Miguel
Comment 6•20 years ago
|
||
This is invalid. The innerHTML setting wasn't putting the form controls inside
the table, so of course they were not sent.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•