Closed Bug 97483 Opened 24 years ago Closed 2 years ago

forms not closing properly

Categories

(Core :: DOM: Editor, defect, P5)

defect

Tracking

()

RESOLVED INCOMPLETE
mozilla1.4beta

People

(Reporter: TucsonTester2, Unassigned)

Details

(Whiteboard: ? days; oic)

Inserted a form into a web page, a basic drop down menu after the drop down menu I entered an image and continued adding items to the page, later decide to remove image, and did so but in doing this it also removed several other items from the page. Used undo several times looked at code noticed error. the image had been inserted before the end of the form along with the other items removing the image removed everything after the code for the image until the end of the form. actual code that was present <body> <form name="gotolocation" method="Post"> <select name="dropdown" size="1"> <option selected="" value="#">==You Are On The Menu Page== </option> <option value="http://ebay.com">ebay </option> <option value="http://www.aol.com">aol </option> <option value="http://www.tomshardware.com">Tom't hardware </option> <option value="http://w3.org">w3c </option> </select> <input type="button" onclick="document.location = document.gotolocation.dropdown.options [document.gotolocation.dropdown.selectedIndex].value;" value="GO"> <p> Choose your destination and click on the button to go there.<br> <img src="file:///C:/WINDOWS/DESKTOP/5500tower.jpg" alt="big puter" width="640" height="480"> <br> </p> </form> </body> the code that was expected <body> <form name="gotolocation" method="Post"> <select name="dropdown" size="1"> <option selected="" value="#">==You Are On The Menu Page== </option> <option value="http://ebay.com">ebay </option> <option value="http://www.aol.com">aol </option> <option value="http://www.tomshardware.com">Tom't hardware </option> <option value="http://w3.org">w3c </option> </select> <input type="button" onclick="document.location = document.gotolocation.dropdown.options [document.gotolocation.dropdown.selectedIndex].value;" value="GO"> <p> Choose your destination and click on the button to go there.<br> <br> </p> </form> <img src="file:///C:/WINDOWS/DESKTOP/5500tower.jpg" alt="big puter" width="640" height="480"> <br> </body> steps to reproduce 1. open new composer page 2. click on insert then choose html insert a form 3. after the form appears press enter, cursor moves to new line 4. insert something "i inserted an image" results item was inserted with in the code for the form expected code for item would be after </form>
-->jfrancis
Assignee: brade → jfrancis
This works for me using the exact example sumbitted in the bug. I am on Linux with build 2001080814.
Confirming the same error on Linux 2001082908 Followed steps to reproduce and noted image is inside form: eg: </select> <input type="button" onclick="document.location = document.gotolocation.dropdown.options [document.gotolocation.dropdown.selectedIndex].value;" value="GO"> <p> Choose your destination and click on the button to go there.</p> <p><img src="file:///home/webart/Patricia.jpg" alt=" " width="68" height="95"> </p> <p></p> </form> Also noticed that when the form is inserted (when the "insert HTML" dialog closes) the cursor appears to "stick" in the composer - possibly at the end of the form element.
marking NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
oops, forgot OS -> ALL, +regression based on G. Todd's comments
Keywords: regression
OS: Windows 95 → All
Ignore earlier "works for me" - bug exists on 0.9.3 as well Linux 2001080814.
Keywords: regression
096
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla0.9.6
Whiteboard: EDITORBASE; ? days;
Target Milestone: mozilla0.9.6 → mozilla0.9.9
Priority: -- → P3
Target Milestone: mozilla0.9.9 → mozilla1.0
also present on mac os x, build 2001121805. changing platform to all.
Hardware: PC → All
removing EDITORBASE per meeting
Whiteboard: EDITORBASE; ? days; → ? days;
Moving bugs to Mozilla1.1 that are not EDITORBASE+.
Target Milestone: mozilla1.0 → mozilla1.1
The trunk is the wave of the future!
Target Milestone: mozilla1.1alpha → mozilla1.1beta
The days of having a half dozen milestones out in front of us to divide bugs between seem to be gone, though I dont know why. Lumping everything together as far out as I can. I'll pull back things that I am working on as I go.
Target Milestone: mozilla1.1beta → mozilla1.2beta
migrating milestones now that there are more available. i'll pull these back as I work on them
Target Milestone: mozilla1.2beta → mozilla1.4beta
Should this be nominated for topembed?
Whiteboard: ? days; → ? days; oic
QA Contact: sujay → editor
Assignee: mozeditor → nobody
Status: ASSIGNED → NEW

Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.

If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5

It's about the old Composer App.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.