Peter Sanderson

Here is the problem: - In the `... send/components/Outputs/components/Amount/components/Fiat.tsx` there is the problem that it has `handleChange` directly on the input. - In this handler the `errors` are checked, -...

What are info notes? It would be really good to have some drawings in the picture so its clear.

@martinboehm Sorry for late response, I missed your message. Thanks for explanation.

closed in favor of: https://github.com/trezor/trezor-suite/pull/12349

Proof of concept done by Marek: https://github.com/trezor/trezor-suite/pull/11355

Lets not do this before Node19. It has some differeneces and causing troubles. See: https://github.com/trezor/trezor-suite/pull/11820 (Details: https://satoshilabs.slack.com/archives/C02V2PSDNA2/p1711539811017599)

Here is also relevant Github Issue: https://github.com/nodejs/node/issues/46375

Also good read: https://betterstack.com/community/guides/scaling-nodejs/nodejs-timeouts/#timing-out-a-fetch-api-request It says that in node fetch has no timeout, but it seems that its not true > In browsers, fetch() usually times out after a set...

Finally another issue: https://github.com/nodejs/undici/issues/1373 TBH I dont see a good solution to this right now :(

Maybe a solution is to use `undici`. There is a way how to define timeouts globally. ```ts const { Agent } = require('undici'); dispatcher = new Agent({ connectTimeout: 10 *...