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)
Core
Layout: Form Controls
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.
Reporter | ||
Updated•23 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla0.9
Comment 1•23 years ago
|
||
Adding keywords so this doesn't get lost. Gerv
Keywords: mozilla0.9,
nsbeta1
Comment 2•23 years ago
|
||
Setting milestone to mozilla0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
Updated•23 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9
Reporter | ||
Comment 4•23 years ago
|
||
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
Updated•23 years ago
|
Target Milestone: mozilla0.9.1 → mozilla0.9.3
Updated•23 years ago
|
Target Milestone: mozilla0.9.4 → mozilla0.9.6
Comment 6•23 years ago
|
||
Bulk reassigning form bugs to Alex
Assignee: pollmann → alexsavulov
Status: ASSIGNED → NEW
Assignee | ||
Updated•23 years ago
|
Summary: Saving form control state: better detection of state change → Saving form control state: better detection of state change [form sub]
Assignee | ||
Comment 7•23 years ago
|
||
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
Comment 8•23 years ago
|
||
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
Comment 10•22 years ago
|
||
(jkeiser implemented these changes as part of work elsewhere)
You need to log in
before you can comment on or make changes to this bug.
Description
•