Fine-grained PAT creation form fails silently on invalid expiration date #207603
Unanswered
tallneil
asked this question in
Apps, API and Webhooks
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
API
Body
When creating a fine-grained personal access token at https://github.com/settings/personal-access-tokens/new, the form submission fails with no visible error message when the custom expiration date input is rejected by native HTML validation.
Console error observed:
An invalid form control with name='user_programmatic_access[custom_expires_at]' is not focusable.Relevant element:
<input class="form-select FormControl-input" aria-labelledby="expiration-label" min="2026-09-12" max="2027-09-11" style="background: none;" type="date" name="user_programmatic_access[custom_expires_at]" id="user_programmatic_access_custom_expires_at">Impact: The browser blocks submission because the date input is invalid, but since the invalid control isn't focusable/visible in the normal flow, no error is shown to the user — the form just appears to do nothing on submit. Users have no indication why token creation failed or how to fix it.
Expected behavior: The UI should surface a visible, actionable error near the expiration field when the date fails validation (e.g. out of the min/max range), rather than failing silently.
All reactions