Closed
Bug 732008
Opened 13 years ago
Closed 13 years ago
jquery scrollto function with key event doesn't work on camino
Categories
(Camino Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cable_007, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; fr; rv:1.9.2.27) Gecko/20120217 Camino/2.1.1 (MultiLang) (like Firefox/3.6.27)
Build ID: 20120217201925
Steps to reproduce:
I'm writing a webpage with jquery and inside it I have a form (contact form) that appears
there are "cancel" button and I created a script to scroll on top when we click on cancel button or when we type on escape on keyboard
Actual results:
all works well everywhere (all browers) but in camino (I use 2.1.1), escape doesn't work whereas "cancel" button works well.
cancel action scrolls me on top of the page but with escape key, not on full top of page
to reproduce, you need to get vertical scroll
see piece of code (cancel button + escape key) :
// When the "Cancel" button is clicked, close the form
$y('#cancel').click( function() {
$y('#question').fadeOut();
$y('#content').fadeTo( 'slow', 1 );
$y('#footer').fadeTo( 'slow', 1 );
window.scrollTo(0,0);
} );
// When the "Escape" key is pressed, close the form
$y('#question').keydown( function( event ) {
if ( event.which == 27 ) {
$y('#question').fadeOut();
$y('#content').fadeTo( 'slow', 1 );
$y('#footer').fadeTo( 'slow', 1 );
window.scrollTo(0,0);
}
} );
Expected results:
function is same so I should get same result and be on top in pushing escape key
Comment 1•13 years ago
|
||
> all works well everywhere (all browers)
Including Firefox 3.6, whose rendering and JS engine we share?
(3.6 is still the current long-maintenance-cycle release for Firefox, so it has non-trivial usage. If you care about Camino usage, you should care about Firefox 3.6 as well, since it's almost certainly orders of magnitude more.)
indeed, I'm not using this old firefox build :-(
I had missed this part
sorry for the noise
NIko
Comment 3•13 years ago
|
||
If it's fixed post-1.9.2 it's almost certainly a dup, but rather than try to find it I'll just call it wontfix
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•