Secure field 0.9.0
Optional client-side encoding for form fields — transport helper only; TLS is required in production.
Demo only. Client-side encoding is not encryption. Never store passwords or API keys.
Usage
<velin-secure-field type="email" name="contact" label="Email"></velin-secure-field>
import '@birdapi/velinstyle/secure';
Not in the default IIFE bundle — import the subpath to keep bundle size small.
Events
On change, dispatches velin-secure-submit with detail.payload and detail.name.
Important
Transport aid only — not a replacement for HTTPS, server validation, or secret management.