search

KawaiiBASIC / classilla

Automatically exported from code.google.com/p/classilla
0 stars 0 forks source link

Login box failure [login.yahoo.com] #120

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Some of the Yahoo! login screens still don't work. We should try to make a
test case out of

https://login.yahoo.com/config/login_verify2?&.src=ym

and see why toCheck keeps coming up null when we click Submit.

I promised improved performance to Chuck B and others, so we need this too.

Original issue reported on code.google.com by classi...@floodgap.com on 18 May 2010 at 4:13

GoogleCodeExporter commented 9 years ago 
Yahoo's own UI documentation doesn't even match with this. It's like the event
listener is coughing up an object out of thin air. Closures maybe?

Original comment by classi...@floodgap.com on 31 May 2010 at 2:47

GoogleCodeExporter commented 9 years ago 
Closures are defined, and do test okay.

SeaMonkey 2.0.4 on OS X throws a null toCheck also, when the form is 
incompletely
filled out. However, it DOES work when you click the button. I'm having trouble
getting its Venkman to reliably break at the point I think it should (I like
Classilla's Venkman better).

Original comment by classi...@floodgap.com on 31 May 2010 at 3:13

GoogleCodeExporter commented 9 years ago 
Finally got a trace in Firefox 3.6.3 with Firebug. And guess what? It's not
JavaScript; toClick is null there too!

Maybe we're not handling the submit event correctly, which would (surprise 
surprise)
mean this is a DOM issue.

Original comment by classi...@floodgap.com on 31 May 2010 at 3:31

GoogleCodeExporter commented 9 years ago 
And indeed the submit event doesn't make it to the FORM when JavaScript is on,
presumably because the onClick fails.

Original comment by classi...@floodgap.com on 31 May 2010 at 4:07

GoogleCodeExporter commented 9 years ago 
It seems like the event is getting returned marked to consume rather than 
eIgnore.

Original comment by classi...@floodgap.com on 31 May 2010 at 10:55

GoogleCodeExporter commented 9 years ago 
Dropping for 9.2. It seems like this is a lower level DOM issue than I'm 
willing to
fix with 9.3 in the not-too-distant future ready to cover over DOM anyway. FTR, 
the
page also works in 1.7, so the DOM upgrade will solve this.

Original comment by classi...@floodgap.com on 31 May 2010 at 11:14

GoogleCodeExporter commented 9 years ago 
By sheer dumb stupid luck I stumbled over several issues that repair this 
problem and
several others.

M67873
M192170
M211634/m
M216237
M217562
M226462/m
M233142/p

All applied. Fixed! Too bad Yahoo Mail still doesn't work right, but at least 
this is
solved.

Original comment by classi...@floodgap.com on 3 Jun 2010 at 2:22