Closed Bug 69738 Opened 23 years ago Closed 22 years ago

Saving form control state: better detection of state change [form sub]

Categories

(Core :: Layout: Form Controls, defect, P2)

defect

Tracking

()

VERIFIED INVALID
mozilla1.0.1

People

(Reporter: pollmann, Assigned: alexsavulov)

References

Details

This bug is to track a more accurate implementation of state change detection
for form controls.

Currently, we compare the default value (content attribute "value") with the
current value of the widget, with parallels for
selects/options/defaultSelected/selected

The new implementation should probably make note whenever the state changes,
regardless of what happens to the content attribute "value" or "selected", and
either store the original state for later comparison, or just store a binary
indicating that there was a change.  Please attach suggestions / comments /
concerns below.
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9
Adding keywords so this doesn't get lost. 

Gerv
Keywords: mozilla0.9, nsbeta1
Setting milestone to mozilla0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
QA Contact Update
QA Contact: bsharma → vladimire
Target Milestone: mozilla0.9.1 → mozilla0.9
Since there are not ill behaviours reported as a result of our current
implementation, I'm postponing this to 0.9.1 (think this was supposed to be
pushed there before anyway!)
Target Milestone: mozilla0.9 → mozilla0.9.1
Target Milestone: mozilla0.9.1 → mozilla0.9.3
Missed 0.9.3.
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Target Milestone: mozilla0.9.4 → mozilla0.9.6
Bulk reassigning form bugs to Alex
Assignee: pollmann → alexsavulov
Status: ASSIGNED → NEW
Summary: Saving form control state: better detection of state change → Saving form control state: better detection of state change [form sub]
Blocks: 104166
pushig to a future milestone based on Pollmann's comment that says:

"...Since there are not ill behaviours reported as a result of our current
implementation, I'm postponing this ..."

Looks like this is not a big concern issue anyway (but maybe I'm wrong)
Target Milestone: mozilla0.9.6 → mozilla1.0
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → INVALID
(jkeiser implemented these changes as part of work elsewhere)
verifying based on coments
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.