fix(ui): standardize non-busy label ellipsis to single character #479
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/MAPPS-417-placeholder-ellipsis"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements MAPPS-417 (follow-up to MAPPS-410): standardizes the ellipsis glyph in non-busy user-visible labels to the single-character
…(U+2026), completing the glyph unification MAPPS-410 did for busy/loading labels.Change
22 input
placeholder:values and visible menu/action labels (search placeholders across tickets/contacts/assets/projects/settings/knowledge-base/portal/global-search and the three entity pickers, plus "Select technician…", "Manage templates…", "Project description…", "Type your message…", the KB "How to …" and Markdown placeholders, and the form.rs default "Search…") now use…instead of the three-ASCII-dot....Scope
String-literal edits only: 22 insertions / 22 deletions, one glyph each, no imports touched. Deliberately left untouched: doc/line comments mentioning "Loading..."/"Custom..." (e.g. profile.rs, layout.rs, lib.rs), the
layout.rsdocument.titlesentinel that compares against the legacy ASCII"Loading...", the already-compliant profile.rs "Custom…" button, and all code...(ranges, struct-update, rest patterns).Verification
grep -rn 'placeholder:.*\.\.\.' src/returns nothing; no em-dash introduced (only…). CI runs fmt/clippy(-D warnings)/wasm-build/tests.A pre-existing em-dash in a theme-picker WCAG-lock label (unrelated to this ellipsis work) was spotted during the sweep and is tracked separately.
#MAPPS-417