Don't null out reserve/target if user cancels update

Previously we were accepting the null return value from a user-cancelled window.prompt call, which got coerced to 0 when dispatching + persisting the updated reserve or target value. Escaping out of a prompt should now leave the existing reserve/target intact.