You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typically fields have a label with the css "for" attribute so that styling can be precise. When using labels on Lexical fields however the attribute is for="field-undefined" even when a label is explicitly declared:
n-a-t-j-b
changed the title
UI Fix: Lexical Fields use "undefined" for name in css label element property "for="
UI Fix: Lexical Fields use "undefined" for name in css label element attribute "for="
Dec 18, 2024
Describe the Bug.
Typically fields have a label with the css "for" attribute so that styling can be precise. When using labels on Lexical fields however the attribute is for="field-undefined" even when a label is explicitly declared:
<label class="field-label " for="field-undefined">Introduction</label>
versus the norm (author in this example) which is for="field-(insert field name here)":
<label class="field-label " for="field-author">Author<span class="required">*</span></label>
Reproduction Steps
Create a richText field in your config (with or without a label element):
Inspect the output of the Admin Panel for that field using dev tools.
Expect to see:
<label class="field-label" for="field-intro">Introduction</label>
But instead you get:
<label class="field-label" for="field-undefined">Introduction</label>
Environment Info
The text was updated successfully, but these errors were encountered: