easyjet web site too clever by half, prevents basic entry of From: airport

Here is a screenshot:

Since it's a still, it doesn't show quite how distracting it is to have a field of vision that keeps violently changing, while one is trying to do something.  I was trying to do this thing, but I'm now busy trying to un-hypnotise myself from fade transitions, and give my attention to the actual form again.  Why do websitetards do this?

My screenshot above does catch it mid-fade, which gives you some idea.

Now, what was I doing?

Trying to set the From: field, which is an airport.  I type LGW, which is gatwick, and it gives me a drop-down with a single item, which I select.  But it fails.  Nothing happens.  Confusingly, the light gray example text is "e.g. London Gatwick", but that isn't its value; it still has no value.

Since I've done battle with this form before, I can remember what the geektard-induced fault with their web site is: the victim is not allowed to set the From: field to the same value as the To: field, and the To: field is set to gatwick.  Easyjet don't do flights with departure airport and destination airport the same, so it's almost perfect logic.  Unless you think about it for more than ten seconds, or try to actually use the web site, at which point you immediately realise it's flawed.

The form is kindly pre-filled with the previous values used.  Fine.

If the user is doing something else, other than reusing the previous values, then they have to enter new values in the fields.  In this case, it will not be unusual for the departure airport this time to be whatever the arrival airport was last time.  Here, LGW.  By refusing to have the fields set, temporarily, to the same airport, the form is obstructing the customer who knows where they are going from and to, and wants to just enter that information. 

Note that this needed special-casing.  If they had just declined to meddle with it and make it more complicated, it would have been fine.  Whereas the effort to realise "it's an anti-feature; don't bother with it at all" was around 10 seconds thinking, the effort to implement it (and test, sign-off, etc) will have been around 10 man-days.

Workaround: set the To: field, and then go back to the From: field.

Lesson: never let some geektard's presumptions about reality end up as a user-visible constraint.