If the user does this, the hidden form field retains the id of the employer the user clicked on, which is probably not what we want, I think?
DoD:
If a user types something that is not in the list, we don't save any data about employer.
If the user does this, the hidden form field retains the id of the employer the user clicked on, which is probably not what we want, I think?
DoD:
If a user types something that is not in the list, we don't save any data about employer.
Project | Branch | Lines +/- | Subject | |
---|---|---|---|---|
mediawiki/extensions/DonationInterface | master | +3 -0 | Reset employer_id each time a new search starts |
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T228765 Epic: matching gifts HEP integration (was employer field V2) | |||
Resolved | jgleeson | T256838 In the DonationInterface form, handle case in which a user clicks on an employer from the dropdown, then types the name of an employer not on the list |
Change 610140 had a related patch set uploaded (by Jgleeson; owner: Jgleeson):
[mediawiki/extensions/DonationInterface@master] Reset employer_id each time a new search starts
I +2ed this but I'm a little concerned about the opposite case where someone accidentally types after entering their correct employer. I wonder if the kind of locked styling would help with. I played with it for 10 minutes but I don't want to go too far out of scope.
Change 610140 merged by jenkins-bot:
[mediawiki/extensions/DonationInterface@master] Reset employer_id each time a new search starts