[spam]::[Ietab] Lawson portal somehow doesn't make Login button
sensitive
Karr, David
david.karr at wamu.net
Tue Jan 17 14:41:28 EST 2006
If it helps, I've been able to narrow this down to specific javascript
event processing that works in IE, but is not happening in IETab in
Firefox.
There is a line in the HTML somewhat like this:
<input type="password" name="_ssoPass" value="" onkeyup="keyPress();"
size="17" maxlength="50">
When I execute this in IE, the "keyPress()" function gets called when I
press a key. When I execute it in IETab, it never gets executed. When
I instead changed the line to this:
<input type="password" name="_ssoPass" value=""
onkeypress="keyPress();" size="17" maxlength="50">
The page works the same in both IE and IETab.
Note that I don't have the option of changing the real code to use
"onkeypress" instead of "onkeyup". It's provided by a vendor company
(Lawson).
> -----Original Message-----
> From: ietab-bounces at mozdev.org
> [mailto:ietab-bounces at mozdev.org] On Behalf Of Karr, David
> Sent: Tuesday, January 17, 2006 1:59 PM
> To: ietab at mozdev.org
> Subject: [spam]::[Ietab] Lawson portal somehow doesn't make
> Login button sensitive
>
>
> My company uses Lawson for time reporting. When I use it in
> IE, the login screen makes it so that the Login button only
> becomes sensitive after some content is entered in both text
> fields (user and password). When I use it in IETab, the Login
> button never becomes sensitive. I tried to trace back
> through the javascript to understand why this might have
> happened, but I'm unsure what might be wrong.
>
> The javascript on the page first makes a list of all the
> "text" and "password" fields. There is code that sets the
> login button to be sensitive if all the fields are non-empty,
> but for some reason, it appears that it only sets up that
> function to be called (on a 500 ms
> timeout) if the browser is NOT Internet Explorer.
> Nevertheless, when I run it in IE, the button does become
> sensitive. I don't know how it's working in IE, or why it
> doesn't work in IETab.
>
> I did verify that "navigator.appName" is set to "Microsoft
> Internet Explorer" in IETab (by writing a simple html that
> pops up an alert with the value).
> _______________________________________________
> Ietab mailing list
> Ietab at mozdev.org
> http://mozdev.org/mailman/listinfo/ietab
>
More information about the Ietab
mailing list