There are 2 password forms:
1.On the main page https://booking.flyfrontier.com/ It's filled both with new and old parsing.
2.When to click sing-in on https://booking.flyfrontier.com/Flight/Select . It's not filled nor with new nor with old parsing. The problem is that there is not <form> flag and so it's considered as big synthetic which actually contains sign-up + sign-in form. It's hard to parse it right:

Fields:
email: 420638584, type=text, autocomplete=off
email: 420638584, type=text
confirm_email: 2380180936, type=text
password: 2051817934, type=password, autocomplete=off
confirm_password: 822190368, type=password
first_name: 1938669551, type=text
middle_name: 2842732069, type=text
last_name: 3389759488, type=text
: 4203909268, type=select-one
gender: 357851563, type=select-one
birth_date: 2138399214, type=text
phone: 1794903826, type=tel
address1: 2267517795, type=text
address2: 1236818338, type=text
city: 2098554694, type=text
state: 1878375253, type=select-one
zip_code: 2512693257, type=text
email: 420638584, type=text, autocomplete=off
password: 2051817934, type=password, autocomplete=off

New parsing says 
Username element : email 
 and 
New password element : password that's correct :).

So it's not regression in new parsing, that's good. In future we can think how to parse such complex forms.