Closed Bug 25625 Opened 26 years ago Closed 26 years ago

Test bug for bug 25624 to check for bugzilla dbase corruption

Categories

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

Product:
Core
Component:
Layout: Form Controls
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED INVALID

People

(Reporter: sidr, Assigned: karnaze)

Details

(Whiteboard: Please leave alone as example of bug 25624 problem)

Please leave this alone for now; either adding a comment to this using build 2000-01-28-08-M14 will cause data corruption, or it won't, and bug 25624 will be updated accordingly.
Seeing the bug 25624 problem; now to see if the incorrect <SELECT> values visible above get submitted.
Severity: major → blocker
Component: HTML Form Controls → All
OS: Windows NT → All
Priority: P3 → P1
Product: Browser → Architecture
Hardware: PC → All
Target Milestone: M1
Version: other → unspecified
Quoting from message received when submitting the previous comments: --------- Changing product means changing version and component.You have chosen a new product, and now the version and/or component fields are not correct. (Or, possibly, the bug did not have a valid component or version field in the first place.) Anyway, please set the version and component now. Product:Architecture ----------- This looks like data corruption; check the "View Bug Activity" link to see what got changed without my having touched the <SELECT>s, other than Version and Component on the intercept page quoted above. Yech.
Whiteboard: Please leave alone as example of bug 25624 problem
Resolving as INVALID to remove from NEW radar.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → INVALID
Setting <SELECT>s to values other than their first item to recheck with 2000-01-28-12-M14 on WinNT.
Severity: blocker → normal
Component: All → HTML Form Controls
OS: All → Windows NT
Priority: P1 → P3
Product: Architecture → Browser
Hardware: All → PC
Version: unspecified → other
Adding a comment just to resubmit and check this again; it appears that this problem has been fixed.
VERIFYing to get this off all radars; bug 25624 is fixed.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.