Closed Bug 70482 Opened 24 years ago Closed 23 years ago

[CBX][LST]Selects do not properly process the "success" for submission

Categories

(Core :: DOM: Core & HTML, defect, P2)

defect

Tracking

()

VERIFIED WONTFIX
mozilla0.9.6

People

(Reporter: rods, Assigned: john)

References

Details

selects need to check to see if they have any items selected in order to pass back "true" in their IsSuccessful method. Currently, they just check for "name" and for "disabled"
accepting
Status: NEW → ASSIGNED
Priority: -- → P2
Hardware: Macintosh → All
Target Milestone: --- → mozilla0.9.1
As per HTML 4.01 spec "17.13.2 Successful controls"
Erci, this was the bug I was talking about. I will reassign it to you because you are changing the way submission works.
Assignee: rods → pollmann
Status: ASSIGNED → NEW
Target Milestone: mozilla0.9.1 → mozilla0.9.3
Missed the 0.9.3 train.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Eric is no longer here . . . ---> Kevin
Assignee: pollmann → kmcclusk
Reassigning back to Rod.
Assignee: kmcclusk → rods
Target Milestone: mozilla0.9.4 → mozilla0.9.6
Over to eric
Assignee: rods → evaughan
What the heck does it matter what the IsSuccessful() method does if submission Does The Right Thing? Anyway, this is all changing with sicking's enhancments to the bug 34297 patch. There will be one function now--basically an nsFormSubmitter will call the control with a pointer back to itself, and the control will call an AddNameValuePair() method (or something similar) on the FormSubmitter. No arrays are needed, no annoying copying. If disabled or no name, nothing is passed back to the submitter and thus nothing is submitted. This *will* be more efficient memory-wise and even speed-wise (less copying to do). And the external effects are precisely the same as the (apparently) multi-pass algorithm recommended in the spec. If someone can think of a reason why we should split these methods up, speak now or ... you get the idea. Relevant spec reference: http://www.w3.org/TR/html4/interact/forms.html#h-17.13.3 The spec is over-specifying here and I see no reason to do what it says over this method when the effects (from the point of view of the web developer and the user) are precisely indistinguishable. Setting dependency and adding sicking in case there is discussion to be had.
Depends on: 34297
Looks like you have a handle on it John.
Assignee: evaughan → jkeiser
OK, there's no discussion. Closing WONTFIX, there's no reason to do it this way.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
verifying per developer's coments...
Status: RESOLVED → VERIFIED
Component: HTML: Form Submission → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.