Closed Bug 62749 Opened 25 years ago Closed 25 years ago

missing Interview selection

Categories

(Toolkit :: Form Manager, defect, P3)

defect

Tracking

()

VERIFIED INVALID

People

(Reporter: tracy, Assigned: morse)

Details

seen on commercial builds: windows 2000-12-13-06-Mtrunk linux 2000-12-13-06-Mtrunk mac 2000-12-13-04-Mtrunk open Tasks | Privacy and Security | Form Manager next to the Demonstration selection there should be an Interview selection. It is missing workaround to this selection being missing is to select View Captured Form Data instead and edit the information there.
That ain't a bug, it's a feature. (I've always wanted to say that in a situation when it was really true and this time it is.) The dialog that comes up when you view captured form data used to be just that -- a means of viewing your data but not entering new data. Last night I checked in a completely new dialog for use here that allows you to both view and edit your data. It completely deprecates the need for the interview form. So the interview form, which was contraversial for several reasons, was removed from the menu. The objections with the interview form were: 1. It was written in html and therefore difficult to internationalize 2. It was long 3. People didn't know what "interview" meant (although it seemed obvious to me). Someone else just discovered this new dialog this morning and filed bug b2727 on it. You might want to look at my comment in that bug report as well.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
That other bug number is bug 62727 (sorry for the typo).
BTW, the fact that you figured out what you referred to as a "work-around" so quickly is actually an encouraging sign. I was wondering what whether users who were familiar with the old "interview" choice would realize what its replacement was.
marking verified invalid but, look at new bug# 62764 regarding functionality of new form manager
Status: RESOLVED → VERIFIED
Product: Core → Toolkit
QA Contact: tpreston → form.manager
You need to log in before you can comment on or make changes to this bug.