Closed daun closed 10 months ago
Name | Link |
---|---|
Latest commit | ccc0ef990aac087a7c01f84ac533828a0ffd4e27 |
Latest deploy log | https://app.netlify.com/sites/splendorous-kataifi-9ae281/deploys/650870b37e787a0008aea67a |
Deploy Preview | https://deploy-preview-152--splendorous-kataifi-9ae281.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Nice! In the demo's text it says that the keyboard focus is being kept. Is this really the case? The form is being replaced after a click on submit
, so the focus will go to the body, won't it?
With the newest Forms Plugin update, we're using the id to build a selector, which should make this work. Let me double-check, though!
It works. Phew 🥵 The wording is slightly wrong, then — the focus isn't kept but rather restored. For this intro text, I don't think it matters. What do you think?
Ah ok now I understand! The focus will be moved to/kept on the submitted <form>
element, right?
Yes! With the current implementation, it will always (re-)focus the form itself, not keep the focus inside the form.
Description
Checks
master
branchnpm run lint
)npm run test
)