Skip to content

fix(properties): replace default-font-id datalist with a select#81

Merged
u8array merged 1 commit into
mainfrom
fix/default-font-id-input
May 21, 2026
Merged

fix(properties): replace default-font-id datalist with a select#81
u8array merged 1 commit into
mainfrom
fix/default-font-id-input

Conversation

@u8array
Copy link
Copy Markdown
Owner

@u8array u8array commented May 21, 2026

No description provided.

The text input with list="zpl-default-font-ids" hit a browser
datalist quirk: after a datalist suggestion has been picked and the
component re-renders (e.g. when a Labelary preview kicks in), Chrome
and Firefox keep the previous suggestion bound to the input and the
next keystroke gets discarded. The field looked editable but onChange
stopped firing.

Replaces the input with a real select that lists the same union of
font IDs (built-ins + every ^CW alias + every preview binding), plus
an explicit "(none)" option for clearing the default. Selects do
not carry the autocomplete state that broke the datalist input, so
the field stays responsive across re-renders.

Drops the now-unused datalist element and adds the new
label.defaultFontIdNone locale key across all 32 locales.
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request replaces the text input and datalist for the default font ID with a select dropdown in the Properties Panel. It also introduces a 'none' option for the font selection and adds the corresponding translation key 'defaultFontIdNone' across multiple locale files. I have no feedback to provide.

@u8array u8array merged commit 9bbe10b into main May 21, 2026
1 check passed
@u8array u8array deleted the fix/default-font-id-input branch May 21, 2026 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant