Send tab - Issues
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.6k
- Forks
- 3.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 61
Description
Hi,
I am using Electrum 4.0.2 via AppImage on Linux, with Trezor Wallet with p2wpkh (SegWit native) addresses.
When I want to send new transaction, I populate Pay To, Description and Amount fields. Then I click Pay. New window titled "Confirm Transaction" will appear, which allows me to adjust Fee, or go to Advanced mode. When I click Send on this window, Electrum correctly initializes Trezor interface, I can enter PIN and log in to Trezor and broadcast it. Everything is fine.
Issue 1: Immediately when I click Pay on Send tab, transaction appears in Outgoing payments list, status is shown as PAID. If I cancel transaction or want to amend details, transaction is actually not PAID, and there is no way I can return to this transaction ever again. I can only copy details or delete is from the Outgoing payments list. There is no Tx ID, because it has never been send.
Issue 2: If I click Cancel from Confirm Transaction window, all pre-filled details I entered previously on main Send Tab are gone. I need to re-enter everything again. Please change this behaviour so Electrum preserves data which I enter in Pay to, Description and Amount fields.
Issue 3. If I click Advanced and then X at the top of the window or Close button, same thing happens again. Pay to, description and Amount fields are empty.
Issue 4: GUI inconsistency: To actually Send transaction, I need to click Send on Confirm Transaction window, or Finalize on Advanced window. Please make button naming consistent.
Issue 5: What is the purpose of Outgoing payments list? My transaction, when send correctly, will appear on History tab. And there is no way to edit outgoing payments, each time I click Pay, Electrum just blast a new transaction to the list, always shown as "Paid". So it's not really useful at the moment.
Thanks for your all hard work. I love Electrum. Peace :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Send tab, the Confirm Transaction window, and its Advanced view, reproducing cancellation and closing flows with the listed Pay To, Description, and Amount values. Trace how outgoing payments are created and how transaction details are retained or cleared; done means cancelled or amended transactions are not marked paid, entered values persist, and the send actions use consistent labels.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend, payments
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100