Providing OMS value and then navigating to the next button through the tab and pressing enter caused the OMS input to re-display on the UI. This was because of the programmatic behaviour of the form handler and the button handler colliding, causing both the handlers to be run at the same time, re-updating the condition which displays the OMS input on the UI.
Screenshots of Visual Changes before/after (If There Are Any)
IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance
Related Issues
Closes #
Short Description and Why It's Useful
Providing OMS value and then navigating to the next button through the tab and pressing enter caused the OMS input to re-display on the UI. This was because of the programmatic behaviour of the form handler and the button handler colliding, causing both the handlers to be run at the same time, re-updating the condition which displays the OMS input on the UI.
Screenshots of Visual Changes before/after (If There Are Any)
IMPORTANT NOTICE - Remember to add changelog entry
Contribution and Currently Important Rules Acceptance