Initial checklist
Affected packages and versions
@milkdown/crepe 7.21.3
Link to runnable example
No response
Steps to reproduce
- Mount a Crepe editor with default features in any host app.
- Open Chrome DevTools on the page.
- Check the Issues panel.
Expected behavior
Crepe's internal input elements carry an id or name attribute, so host pages pass Chrome's form-field audit.
Actual behavior
Chrome DevTools reports "A form field element should have an id or name attribute". The violating node is the link-edit input (class "input-area", placeholder "Paste link..."), created at editor startup without id or name. The image caption input (class "caption-input") has the same gap. As a workaround we stamp attributes onto these inputs via a MutationObserver in the host app.
Runtime
Chrome
OS
Windows
Build and bundle tools
esbuild
Initial checklist
Affected packages and versions
@milkdown/crepe 7.21.3
Link to runnable example
No response
Steps to reproduce
Expected behavior
Crepe's internal input elements carry an id or name attribute, so host pages pass Chrome's form-field audit.
Actual behavior
Chrome DevTools reports "A form field element should have an id or name attribute". The violating node is the link-edit input (class "input-area", placeholder "Paste link..."), created at editor startup without id or name. The image caption input (class "caption-input") has the same gap. As a workaround we stamp attributes onto these inputs via a MutationObserver in the host app.
Runtime
Chrome
OS
Windows
Build and bundle tools
esbuild