Closed
Bug 17783
Opened 25 years ago
Closed 24 years ago
Back button on 2nd screen of new testcase entry not functional
Categories
(Webtools Graveyard :: Litmus, defect, P3)
Webtools Graveyard
Litmus
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: lchiang, Assigned: zach)
Details
Back button on 2nd screen of new testcase entry not functional
prime/testzilla 11/1/99
1) Click Enter a new Testcase link
2) First entry screen appears. Enter some items in any of the fields
3) Click Next button
4) Second entry screen appears
5) Click Back button
Actual results: Nothing happens. You are still on the second entry screen.
Expected results: Go back to the first entry screen.
Right now I can't think of a way to do this w/o using javascript. I've removed
the back button for the time being, but will leave this bug open, in the hopes I
can think of a way to add this.
dshea is no longer here - not sure who will inherit testzilla.
Assignee: dshea → lchiang
Status: ASSIGNED → NEW
Assignee | ||
Comment 5•24 years ago
|
||
Does this mean that tz is dead for now on? I have been writting a testcase
management system, talked to Asa and Endico about it. I am far along,
writing code...I could take the owner for the component.
If you take ownership, that would be good. We've dropped looking into this for
the time being (here at Netscape) so no action on this bug so far.
Assignee | ||
Comment 7•24 years ago
|
||
Ok, Can someone set the component owner to me? I'll ping Asa about it
later if it doesn't happen.
Assignee | ||
Updated•24 years ago
|
Assignee: lchiang → zach
Assignee | ||
Comment 8•24 years ago
|
||
Because Netscape has decided not to continue 'testzilla', I am taking
ownership of all nakedmolerat bugs (the new codename), while I
continue coding it.
Assignee | ||
Comment 9•24 years ago
|
||
This doesn't matter, I have no 2nd screen!
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Updated•18 years ago
|
QA Contact: lchiang → litmus
Updated•8 years ago
|
Product: Webtools → Webtools Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•