Bug 16930 – Monster.com claims to no longer support Safari

• Status: RESOLVED
• Resolution: WORKSFORME
• Component: Forms

[Thaddeus Cooper]

Monster has done something so as not to be compatible with Safari. Here is the last word I received from them in an email to customer support:

I understand from your mail that you are using the Mac OS X (Leopard - 10.5.1 Build 9B18) as operating system and browser as Safari 3.0.4(5523.10). 

I am sorry to inform you that Monster currently do not support Safari 3.0 and Mac OS X (10.5). 

Monster currently supports the following browsers on the PC: 

1. IE 6+
2. Netscape 7+

However, I will take your email as a feedback and I have listed your email as complaint in our Customer Listening System which is viewed by all levels of Monster's management.

[Mark Rowe (bdash)]

In what way are they not compatible?  What doesn't work on their website?

[Thaddeus Cooper]

This problem manifests itself when a user attempts to login to the monster.com Website. When attempting to login the user types their username and password and presses return in the password textfield, and are immediately returned to a login screen to attempt the login again. Repeated attempts result in the same behavior. Tech support at Monster were able to login to the account using the same username/password pair I was using -- but apparently the login process does not work with Safari based on email I received from Monster.com.

[David Kilzer (:ddkilzer)]

Confirmed with a local debug build of WebKit r29833 with Safari 3.0.4 (523.12.2) on Mac OS X 10.4.11 (8S165).

Clicking the Login button image works, but hitting Enter from either the username or password field fails.

[David Kilzer (:ddkilzer)]

Hitting Enter on either form field fails in both Safari 2.0.4 (419.3) and Safari 3.0.4 (523.12.2) on Mac OS X 10.4.11 (8S165), so this is not a regression.

[David Kilzer (:ddkilzer)]

On success (clicking the image), the form variable named __EVENTTARGET is set to:

__EVENTTARGET=MasterPage1%3ABodyContent%3AMyLogin%3AmonsLogin

On failure (hitting Enter), the form vriable named __EVENTTARGET is empty:

__EVENTTARGET=

[David Kilzer (:ddkilzer)]

In Firefox 2.0.0.11, hitting Enter on the username field is apparently prevented via JavaScript (the form is not even submitted), but hitting Enter on the password field successfully submits the form and logs you in.  Clicking on the Login image also logs you in.

[David Kilzer (:ddkilzer)]

With Opera 9.24, hitting Enter on the username field submits the form and fails (similar to Safari; did not check the __EVENTTARGET variable) while hitting Enter on the password filed successfully logs in.  Clicking on the Login image logs you in as well.

[David Kilzer (:ddkilzer)]

Created attachment 18885 [details]
Partial reduction

In Safari, hitting Enter in the password field takes you to Yahoo, while doing the same thing in Firefox takes you to Google.

[David Kilzer (:ddkilzer)]

(In reply to comment #8)
> Created an attachment (id=18885) [edit]
> Partial reduction

The partial reduction shows that setting location.href does nothing during an onkeydown Enter key event that signals a form submission.

> In Safari, hitting Enter in the password field takes you to Yahoo, while doing
> the same thing in Firefox takes you to Google.

"Passing" for this reduction means going to the Google page.

[Alexey Proskuryakov]

(In reply to comment #6)
> In Firefox 2.0.0.11, hitting Enter on the username field is apparently
> prevented via JavaScript (the form is not even submitted)

I think that's bug 9756 for us.

See also: bug 4847, bug 13011, bug 13012, bug 11420, bug 16886.

[Alexey Proskuryakov]

I don't see any issues on this site any more. Is this still a problem?