User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729) The screen which responds to finding a flight reservation never completes. I've been doing this weekly since January 15 without troubles. The big difference this time is that FF 3.6 upgrade is in use. Previously it was using 3.5.4 (I think). Able to successfully complete the effort—or quickly get an "invalid" message—with SeaMonkey 1.1.18 and Chrome 126.96.36.199. Reproducible: Always Steps to Reproduce: 1. https://webselfservice.alaskaair.com/checkinweb/Default.aspx 2. Choose a city (Portland, Oregon (PDX)) 3. Choose method of selecting flight: Confirmation code 4. Use any 6 letter confirmation code: XXXXXX 5. Click on *Continue* Despite its appeal to wait for up to 90 seconds, it will never finish. It doesn't matter if a valid confirmation code is given or not. Actual Results: Stays on the "Please Wait" screen as long as you care to wait. Tested up to two hours. Expected Results: Proceeds to either an error message saying "The request was not successful" or brings up flight information. Possibly Zotero was added since it last worked as well. http://www.zotero.org/
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.