Environment : Firefox for Android 33.1 Android 4.4.2 Steps to reproduce : 1. Browse to : http://www.southwest.com/flight/flight-status-results.html?originAirport=&originAirport_displayed=Las&destinationAirport=&destinationAirport_displayed=Oak&travelDate=11%2F14%2F2014&flightNumber=&connectingAirport=&flightNumberDetails=&submitButton=Continue 2. Begin to enter in an airport in the "From" or "To" field. Expected results : The Southwest form does not accept solely an airport code (for example OAK or SFO) but instead autocompletes what you type in to something like "Oakland, CA - OAK" or "San Francisco, CA - SFO". On Chrome on android or desktop firefox, as you type in "OAK" a dropdown appears and it auto completes to "Oakland, CA - OAK" Actual results : No drop down or autocomplete appears making it impossible to use the form. The only way to use Southwest's flight information with Firefox for Android would be to memorize the exact syntax of the From and To airports to type them in (for example "Oakland, CA - OAK" or "Chicago (Midway), IL - MDW").

Is this a problem due to "onkeypress" vs "oninput" ?

I wonder if the website has webkit/chrome specific changes for Android?

(In reply to Mark Finkle (:mfinkle) from comment #1) > Is this a problem due to "onkeypress" vs "oninput" ? Looks like it. They've got an older version of jQuery UI autocomplete that only listens for keypress/keydown as well as what appears to be a homebrew "AutoCompleter" class which looks like it was based on jQuery UI: c.bind((a.browser.opera ? 'keypress' : 'keydown') + '.autocomplete', function (C) { Not sure we if should move this to Evangelism and ask them to update jQuery UI autocomplete version (current version supports listening for input events) or dupe this against Bug 737658

I'm working on fixing this in bug 1112212.