fix: use modal for transaction progress in Chrome extension

[WiktorStarczewski]

Replace tab-opening pattern with in-popup modal for transaction progress, unifying UX across all platforms (mobile, desktop, extension).

• Remove isExtension() early return in TransactionProgressModal
• Simplify openLoadingFullPage/closeLoadingFullPage to use modal for all platforms
• Update openConsumingFullPage/closeConsumingFullPage similarly
• Pre-create modal container for all platforms in provider.tsx
• Add smaller font/icon sizes for extension modal
• Re-enable animate-spin for transaction progress spinner

[0xnullifier]

How are transaction which throw error are handled ? I don't see any explicit modal opening in that case or UI flow of any kind

[WiktorStarczewski]

How are transaction which throw error are handled ? I don't see any explicit modal opening in that case or UI flow of any kind

Error Handling is in TransactionProgressModal.tsx:

1. Error detection (lines 51-60):

const success = await dbTransactionsLoop(signTransaction);
if (success === false) {
  setError(true);  // ← Error state is tracked
}

2. Error passed to UI (line 139):

<GeneratingTransaction ... hasErrors={error} />

3. Auto-close prevented on error (line 84):

if (isOpen && hasLoadedOnce && transactions.length === 0 && !error) {

4. Overlay dismissable on error (line 124):

shouldCloseOnOverlayClick={transactionComplete || error}

Error UI in GeneratingTransaction.tsx:

When hasErrors=true and transactionComplete=true:

• Shows Failed icon (line 215):
• Shows "Transaction Failed" header (line 237): t('transactionFailed')
• Shows error description (lines 246-251): t('transactionErrorDescription')
• Shows Done button to close (lines 301-306)

[0xnullifier]

Yeah but if I closed the modal and then it throws error what happens then

[WiktorStarczewski]

Yeah but if I closed the modal and then it throws error what happens then

Ah nice, yeah thats a good point. Let me fix this.