Closed Bug 195889 Opened 22 years ago Closed 16 years ago

byutv.org - setting new time on grid, GO button fails

Categories

(Tech Evangelism Graveyard :: English US, defect, P3)

Product:
Tech Evangelism Graveyard
Component:
English US
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: blbrown1, Unassigned)

References

(
URL
)

Details

(Whiteboard: [proprietary-js])

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030212 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.3b) Gecko/20030212 TV listing grid will not advance when new time set and "GO" button pressed Reproducible: Always Steps to Reproduce: 1. set new time on dropdown 2. press "GO" button 3. wait and nothing happens Actual Results: no change in display Expected Results: new times on grid should have been displayed
Also fails on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 The page appears to be trying to use "Javascript:jump.submit()" to submit a form entitled "jump" (in this link and in the definition of the form are the only places "jump" is used). IE accepts this, mozilla says "jump not defined" in the javascript debugger.
Evangelism. IE accepts window.id as a way to reference objects; Mozilla does not and will not.
Assignee: rogerl → susiew
Status: UNCONFIRMED → NEW
Component: JavaScript Engine → US General
Ever confirmed: true
Product: Browser → Tech Evangelism
QA Contact: pschwartau → zach
Version: Trunk → unspecified
Contact addresses are http://www.byutv.org/contact/ and ctwitty@byu.edu
OS: MacOS X → All
Priority: -- → P3
Hardware: Macintosh → All
Summary: setting new time on grid, pressing "GO" button unproductive → byutv.org - setting new time on grid, GO button fails
Whiteboard: [proprietary-js]
tech evang june 2003 reorg
Assignee: susiew → english-us
QA Contact: zach → english-us
404
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.