My website behaves incorrectly on Firefox ( AJAX lookup feature ), while working right on other browsers ( airportintel.com ) How can I fix this?
The drop-down menu doesn't work and the search filed coding doesn't function properly in Firefox. It works correctly in IE, Safari and Chrome.
I had a programmer install the code but he has been unable to determine why the site doesn't work right when Firefox is the browser. The search field sends the user to a specific airport for more information. Right now the only active airport site is SFO. The rest of the entries are for testing and don't go to a valid site.
Is there are reason for this and maybe a way to correct it. I've tried to clear the cache with no luck.
Chosen solution
If I set a break point in Firebug at lines 80 and 92 in airportdata.js, the highlights appear in the drop-down as designed. But not without them. If I log events on the input, the difference is clear: keydown, keypress, keyup, and change fire, while in the break scenario, the latter 3 are effectively avoided.
Is it the Heisenberg uncertainty principle?
Firefox has had a longstanding issue of firing the keypress event even if preventDefault is run for the keydown event. I'm not sure under what conditions this happens, but your developer could take a look at some possible timing issue here. E.g., Bug #501496 – preventDefault on keydown does not cancel following keypress. If forum members can contribute to the development, please feel free to pitch in. Otherwise, it's generally not helpful to add comments to bugs (unless there is a call for test cases), but you can register on the Bugzilla site and "vote" for them to be fixed. See:
Read this answer in context 👍 0All Replies (4)
On Windows 7, Firefox 20.0.1, it works for me as of 5:35pm Pacific.
There is an error in the Error Console which your developer should look at in case it is having a negative impact in Internet Explorer. Here's what I see there:
Error: SyntaxError: illegal character Source File: http://airportintel.com/ Line: 375, Column: 60 Source Code: if (!IE) { return; } if (document.compatMode && document.compatMode == 'BackCompat') {
I think I see the issue now, clicking an item on the autocomplete works, but trying to arrow down and select with the keyboard does not work. Hmmm...
Chosen Solution
If I set a break point in Firebug at lines 80 and 92 in airportdata.js, the highlights appear in the drop-down as designed. But not without them. If I log events on the input, the difference is clear: keydown, keypress, keyup, and change fire, while in the break scenario, the latter 3 are effectively avoided.
Is it the Heisenberg uncertainty principle?
Firefox has had a longstanding issue of firing the keypress event even if preventDefault is run for the keydown event. I'm not sure under what conditions this happens, but your developer could take a look at some possible timing issue here. E.g., Bug #501496 – preventDefault on keydown does not cancel following keypress. If forum members can contribute to the development, please feel free to pitch in. Otherwise, it's generally not helpful to add comments to bugs (unless there is a call for test cases), but you can register on the Bugzilla site and "vote" for them to be fixed. See:
My developer fixed the problem, but he didn't say for sure if your solution was what he used. Thanks for your help on this. Much appreciated!
Steve