Originally Posted by
SWAVictor
I am unable to recreate the issue you are having.
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. I therefore only spent a minute or so on looking into it further when I returned home. It was not difficult to recreate the
search not updating problem.)
Although I can tell you that if your original search was one-way, you cannot at this time use the "modify search" to change the search to a roundtrip (or vice-verse). In other words on a one-way search both boxes marked "Return" (city and date) will not produce any results.
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. BTW, I've learned to ignore the RT/OW input option due to its poor implementation.
I have made several attempts changing the "From", "To" and "Depart(date)" - and always get the updated search results.
That part of the problem is easily reproducible.
The "no outbound flight selected" error sounds like you are trying to "Continue" without actually selecting a flight.
It does sound that way, but I was
trying to modify my search; that's why I posted about it.
I'd have to look at whether there is a way to inadvertently submit via Continue instead of Modify, but I've not done so. Due to quickly closing the page in annoyance after the timeout message, I can't go back and confirm I copied the error message from the correct tab, or retrace my steps.
If it instead says "No departure airport selected" - then that would be an issue with the flyouts . . we usually see this when a Customer types a space after the airport/city name.
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?
ETA: I just looked at and did a quick test of the trim function in SWA's destination_flyouts.min.js:
Code:
String.prototype.trim=function(){return this.replace(/^[\s\xA0]+/,"")
The RegEx above is incorrect. It "trims" 'dal ' to a character string of length four instead of length three. A
web search for javascript trim prototype pretty much instantly returns a few thousand examples of trim RegEx syntax that works correctly.