Background
During a sweep of input field styling consistency (triggered by issue #39), ImportRepeaterContactsModal.vue was flagged as an outlier.
What was found
The modal contains two narrow compact number inputs (hours and limit) rendered inline within sentences:
w-24 py-1.5 — significantly smaller than the standard modal-input padding/width
- Uses
bg-white dark:bg-white/5 — the pre-standards background pattern, not bg-background-mute dark:bg-white/5
- Cannot directly adopt
modal-input without fighting the fixed narrow width and reduced height
Question
Is this compact inline treatment intentional UX (the field is deliberately small and sentence-embedded, matching the copy "Import at most N contacts"), or was it simply built before the global input classes existed and never revisited?
If intentional: document why and whether a modal-input-compact global class would be appropriate for this pattern if it appears elsewhere.
If not intentional: migrate to modal-input and rewrite the surrounding layout so the inputs are full-width with labels above, matching the modal form standard.
No immediate action required
This is a validation task — determine intent before touching the code.
Background
During a sweep of input field styling consistency (triggered by issue #39),
ImportRepeaterContactsModal.vuewas flagged as an outlier.What was found
The modal contains two narrow compact number inputs (hours and limit) rendered inline within sentences:
w-24 py-1.5— significantly smaller than the standardmodal-inputpadding/widthbg-white dark:bg-white/5— the pre-standards background pattern, notbg-background-mute dark:bg-white/5modal-inputwithout fighting the fixed narrow width and reduced heightQuestion
Is this compact inline treatment intentional UX (the field is deliberately small and sentence-embedded, matching the copy "Import at most N contacts"), or was it simply built before the global input classes existed and never revisited?
If intentional: document why and whether a
modal-input-compactglobal class would be appropriate for this pattern if it appears elsewhere.If not intentional: migrate to
modal-inputand rewrite the surrounding layout so the inputs are full-width with labels above, matching the modal form standard.No immediate action required
This is a validation task — determine intent before touching the code.