The summary places both currencies inside #spent, and this rule prevents the entire combined amount from wrapping. A real wallet in the committed data renders a 435px-wide amount inside a 346px content area at a 390px viewport, cutting off the ETH total and creating horizontal scrolling. This violates the mobile no-sideways-scroll criterion.

The supplied FP-only wallet and empty-form example fit, so those cases alone miss the defect.

show() updates the displayed wallet and resets the summary figures but never hides or clears #rows, #note, or #s3 before requesting the new shard. During a slow request the previous wallet's actions are therefore displayed under the new wallet address. If the request fails, the catch handler changes only the status message, leaving the unrelated action table visible indefinitely.

This can misattribute spending history to another wallet.

decodeURIComponent() runs before wallet validation without handling URIError. A literal percent sign from either the form or URL fragment throws instead of displaying the existing invalid-address message. Submitting it after a successful lookup leaves the previous results displayed and emits an uncaught console error.

Opening the fragment directly instead falls into the metadata-fetch catch, incorrectly reports a data-loading failure, and skips renderAll() and livePrice() even though data/meta.json loaded successfully.

The hashchange listener and Show button are active while the initial metadata request is still pending. Submitting the empty form sets #example and calls fromHash(), which dereferences meta.example while meta is null. A slow connection therefore produces an uncaught TypeError during the required empty-form flow.

The example eventually renders when the metadata arrives, but the console-error criterion is not met.