244641 - values from pull down menu on ASP page are not saved when selected

Status: RESOLVED WONTFIX

(Tech Evangelism Graveyard :: English US, defect)

Description

[Scott McAllister]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040517 Camino/0.8b
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7) Gecko/20040517 Camino/0.8b

To submit hours for work I use an ASP page.  On that page I select my clock in
time from one pulldown menu and my clock out time from another pull down menu. 
The number of hours worked is then calculated from these two times and posted in
another field.  Using Camino and Firefox (on Mac and Windows) the calculated
field remains at zero when times are selected from the pull down menus.  

This site is password protected, thus I can not post the link.

Reproducible: Always
Steps to Reproduce:
1. Enter user name and password to login to the site
2. Select "Manager Hours" link
3. Select Start Time from pulldown menu; and End Time from pulldown menu

Actual Results:  
The field that displays 'Hours' holds a value of 0.

Expected Results:  
The field that displays 'Hours' is supposed to calculate the time difference
between the pulldown menus.

Comment 1

[Ludovic Hirlimann [:Usul]]

If it happens with FF it is nop a Camino bug but rather a seamonkey bug.

Comment 2

[Mike Pinkerton (not reading bugmail)]

-> mozilla

Comment 3

[Mike Pinkerton (not reading bugmail)]

any way to post a minimal test case here?

Comment 4

[Boris Zbarsky [:bzbarsky]]

Scott, are there any errors in the JS console?

Comment 5

[Scott McAllister]

(In reply to comment #4)

===== Tue May 25 2004 ===== 14:08:55 US/Mountain =====
2004-05-25 14:09:36.701 Camino[10466] JS error: HoursName is not defined
2004-05-25 14:09:42.120 Camino[10466] JS error: HoursName is not defined

Comment 6

[Boris Zbarsky [:bzbarsky]]

Sounds like the site assumes all browsers are IE and have window.HoursName ==
document.getElementById("HoursName").  That's not the case in Mozilla....

I suggest contacting the page author and asking him to fix the scripts on the page.

Comment 7

[Scott McAllister]

(In reply to comment #3)
> any way to post a minimal test case here?

just got approved to post this.  am i too late?


function CalculateTime()
{
	var bufferA = Date.parse( ManagerHours.StartTime.value ) ;
	var bufferB = Date.parse( ManagerHours.EndTime.value ) ;
	var number = bufferB-bufferA ;
	ManagerHours.RecordedHours.value = parseInt(number / 60000 )/60
;
}



	Response.Write("<TH Align=Center><SELECT Name=""StartTime""
onChange=CalculateTime()>" & vbCrLf)

	temp = 420
		For i=0 To 67

			Response.Write("<OPTION VALUE=""" &
DateAdd("N",temp,HiddenDate) & """>" & DateAdd("N",temp,0) & vbCrLf)
			temp=temp+15
		Next
	Response.Write("</SELECT></TH>")
	
	
	Response.Write("<TH Align=Center><SELECT Name=""EndTime""
onChange=CalculateTime()>" & vbCrLf) 
	temp = 420
		For i=0 To 67

			Response.Write("<OPTION VALUE=""" &
DateAdd("N",temp,HiddenDate) & """>" & DateAdd("N",temp,0) & vbCrLf)
			temp=temp+15
		Next
	Response.Write("</SELECT></TH>")
	Response.Write("<TH Align=Center><Input TYPE=Text
Name=""RecordedHours"" SIZE=4 MaxLength=4 Value=""0""
onChange=CalculateTime()> </TH>" & vbCrLf)

Comment 8

[Chris Lawson (gone)]

Whoever's responsible for maintaining this mysterious site would have to have fixed this, but as it's an internal site, I don't think we really want to waste TE effort on it in the unlikely event that it's still a problem. WONTFIX, but if it's still a problem and it's a widely used time-tracking Web app, we'd obviously reconsider that decision.