Fix footer cost precision, scrolling and display preferences - #674
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Footer costs such as US$0.014889 now display consistently to cents, with positive sub-cent amounts shown as < US$0.01. The footer stays on one horizontally scrollable row, including inside the mobile details panel; cost and organisation popups remain outside its clipping boundary.
Settings → Conversations → Footer provides browser-local visibility controls. Model, conversation cost, user and organisation default on; language, database details, uptime, restart cost, build/timestamp and expert diagnostics default off. Choices update the embedded parent immediately, survive reloads and participate in Reset local preferences. Build information follows the preference at narrow widths too.
Validation: 25 targeted Jest tests passed; changed-JavaScript static lint passed; Chromium candidate-source fixture verified 1297/493/320 px layouts, horizontal scrolling, mobile details, preference persistence and popup visibility. Browser evidence uses mocked API reads, not authenticated backend acceptance. The two supplied screenshot references were unavailable in the worker's actor scope; their descriptions informed the fix.
Native task: #V#task_agent_6e869b3a9169d27fc41db2b732252402. Merge decision: ready on bounded Tier 1 evidence. No deployment requested.