263203 - rubycon.co.jp - IE-specific JavaScript causes empty drop down boxes, form is inaccessible

Status: RESOLVED INVALID

(Tech Evangelism Graveyard :: Japanese, defect)

Description

[Cody]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910

Go to the URL specified above.  You will notice the drop down boxes do not work
under mozilla.  However if you were to open IE and go to that URL the drop down
boxes work just fine.

Reproducible: Always
Steps to Reproduce:
1. Open up mozilla (I am using version 1.7.3)
2. Go to http://www.rubycon.co.jp/en/tech/v-search.asp?type=a
3. You will notice that sites drop down boxes are not compatable with mozilla

Actual Results:  
Drop down boxes would not function as they should.  They will only function
under IE. 

Expected Results:  
The drop down boxes on that website should function as they do for IE.. In other
words they should work.

I am using the Mostly Crystal Theme.
Mozilla 1.7.3
Windows 2000 SP4 (all patches applied)
512MB Crucial RAM
Dual P3 using ABIT-Vp6 motherboard
RAID 0 array

Comment 1

[Bob Clary [:bc] (inactive)]

Error: uncaught exception: [Exception... "Not enough arguments
[nsIDOMHTMLSelectElement.add]"  nsresult: "0x80570001
(NS_ERROR_XPC_NOT_ENOUGH_ARGS)"  location: "JS frame ::
http://www.rubycon.co.jp/en/include/ruby.js :: sh_lb :: line 9"  data: no]

http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-14493106

uses HTMLSelectElement.add(HTMLOptionELement) without specifying the second
parameter. 

Comment 2

[Cody]

So your saying this is the websites fault?  Hard to belive IE has better error
handling than Mozilla..  Because if that site does have a "fault" in the
javascript, that's exactly what your saying...

Comment 3

[Erik Fabert]

This is basically a duplicate of bug 194121 or bug 140427, but it affects a real 
website. Moving to Tech Evangelism-Japanese because it is probably best to 
contact the site in Japanese?

Comment 4

[Erik Fabert]

Attachment: The problematic script

Simply replacing obj.add(oAdd) with obj.appendChild(oAdd) should fix this.

Comment 5

[Cody]

Well even though the site is based off a Japanese company, it is still in
english..  I would think you could easily send them an English e-mail and yeild
a response.  If that was what you were aiming to do?

Comment 6

[Bob Clary [:bc] (inactive)]

Cody, you can send a note to the site as well. Explain that they should either
add a null argument as in  HTMLSelectElement.add(HTMLOptionElement, null) or
change the add to use appendChild as Erik explained. Point them to this bug and
explain the need to test in Non-IE browsers such as Mozilla and Mozilla Firefox.

Comment 7

[Cody]

Alright I sent them the following note:

"This email is about the follow site/function:
http://www.rubycon.co.jp/en/tech/v-search.asp?type=a

The above url contains code that is incompatable with Mozilla/Netscape browsers. 
Your webmaster should either add a null argument as in
HTMLSelectElement.add(HTMLOptionElement, null) or
simply replacing obj.add(oAdd) with obj.appendChild(oAdd) should fix this.

When you are done you should have your webmaster test this function with Mozilla/IE.


Thank You!

Regards,
Cody"

Comment 8

[Johnny Stenback (:jst)]

bc, we support IE's add() method with optional arguments when called on the
options collection. We could fairly easily do the same for select.add(). Think
it's worth it? I seem to remember seeing bugs on this before, but not more than
a few at most...

Comment 9

[Cody]

Well, little incompatibilities such as this may deter some users from using
Mozilla.  I would think it best to support such a simple code argument.  After
all, not all companies will make adjustments to their sites for this browser.  I
still haven't heard back from RubyCon..

Comment 10

[Johnny Stenback (:jst)]

(In reply to comment #9)
> Well, little incompatibilities such as this may deter some users from using
> Mozilla.  I would think it best to support such a simple code argument.  After

True, but there's an endless number of little differences like this, just like
there are between early versions of IE and Netscape 3 etc. We have no interest
in trying to be 100% feature/bug compatible with IE, attempting that would be a
waste of resources.

Comment 11

[Bob Clary [:bc] (inactive)]

I counted about 8 bugs containing a comment with nsIDOMHTMLSelectElement.add and
three instances of it in my logs: msn.com, soho.com and another. So, not a big
deal for now but something to watch?

Comment 12

[Cody]

I agree, however there are some companies that won't use any resources to be as
compatable with Mozilla as well.  However if you wish for people to switch over
it will have to be compatable.  This is the same reason why it took years to
migrate from 16bit to 32bit...


I don't think RubyCon will get back to any of us.  I have emailed them in the
past with no response.  

Comment 13

[Hallvord R. M. Steen [:hallvors]]

404