Originally Posted by
ftnoob
It happened five or six times before I posted, and I tried one more time as a sanity check after posting. Anticipating there might be difficulty recreating the problem, I left the page open while heading off to work. (Of course that proved fruitless due to the rude timeout feature on a page that wasn't even part of a MySouthwest authenticated session.
There are other reasons for sessions besides your MySouthwest login - one would be so that a Customer cannot sit on seats for hours without actually making a purchase
. It was not difficult to recreate the search not updating problem.)
Please elaborate on how you recreated it so that I might be able to do so as well
I have successfully changed searches from RT to OW and OW to RT, so I find your statement that it is not possible quite puzzling.
I stand corrected - apparently this has been fixed since I last used it.
BTW, I've learned to ignore the RT/OW input option due to its poor implementation.
I'm sorry that you don't care for it.
My jaw still hurts from the massive contusion it suffered dropping so violently upon reading the above. With all the CPU cycles consumed by SWA's implementation of the smart city input box, it doesn't even bother to trim whitespace?
I didn't say we weren't working on correcting it . . .