AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Informational 21 Monero

stop keyboard animations rebuilding the hidden dashboard (#3805)

Public commit record

What the developer wrote

Authored by malik1004x

81/100 · Strong
stop keyboard animations rebuilding the hidden dashboard (#3805)

The dashboard stays mounted under every pushed route, and ChartsPage, NewHomePage, CardsView, the coin action row, the unconfirmed balance widget and the wallet list each read MediaQuery.of(context) for a single field. Every viewInsets change while the keyboard animated therefore rebuilt the charts grid, the home page and the wallet list behind the page being typed into. They now use sizeOf / viewPaddingOf, which don't change with keyboard insets.

Measured on the restore-from-seed page (Redmi Note 12, 120Hz, profile build): focusing the seed field went from 16-17 janky frames (build p90 15-19ms) to 1 (build p90 3.7-4.7ms); typing plus dismissing the keyboard went from build p90 11.5-12.5ms to 4.2-4.8ms.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This is a performance improvement, not a security fix. The developers noticed that every time the on-screen keyboard opened or closed, several background dashboard widgets were needlessly redrawing, causing stuttering (janky frames). They replaced broad MediaQuery lookups with narrower ones that only watch the specific values actually needed (screen size and top safe-area padding), so keyboard animations no longer trigger rebuilds. The change improves app smoothness but does not address any vulnerability or protect user data.

Recommended action

No security action needed. Treat as a normal performance/UX improvement. If reviewing, verify that the narrower MediaQuery selectors still provide the intended layout values on devices with notches, foldables, and different orientations.

Security signals we found

No strong security signals were identified.

Risk score

Why this scored 21/100

Our methodology →
Potential impact 2/30
Exploitability 0/25
Stealth signal 0/15
Affected reach 5/15
Confidence 9/10
Evidence quality 5/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.