Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blueprint field display name and handle typing #10081

Closed
mikemartin opened this issue May 15, 2024 · 1 comment
Closed

Blueprint field display name and handle typing #10081

mikemartin opened this issue May 15, 2024 · 1 comment

Comments

@mikemartin
Copy link

mikemartin commented May 15, 2024

Bug description

When creating a field in a blueprint, I've noticed that typing the display name and handle auto-fill are a bit inconsistent. Most of the time it works but every second or third time both the display name and handle seem to get cut off.

Note that this was in Safari. So it could potentially be a Safari browser bug and not a 5.x bug.

Screenshot 2024-05-15 at 8 25 25 pm

How to reproduce

  • Edit Blueprint
  • Create field
  • Select any field type
  • Type display name
  • Click Apply
  • Review field display name

Logs

No response

Environment

Environment
Application Name: Statamic
Laravel Version: 11.7.0
PHP Version: 8.2.19
Composer Version: 2.7.6
Environment: local
Debug Mode: OFF
URL: scratch.test
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: statamic
Database: sqlite
Logs: stack / single
Mail: log
Queue: sync
Session: file

Statamic
Addons: 0
Sites: 1
Stache Watcher: Enabled
Static Caching: Disabled
Version: 5.1.0 Solo

Installation

Fresh statamic/statamic site via CLI

Additional details

Using Safari 16.5

@duncanmcclean duncanmcclean changed the title [5.x] Blueprint field display name and handle typing Blueprint field display name and handle typing May 15, 2024
@duncanmcclean
Copy link
Member

duncanmcclean commented May 15, 2024

This has been fixed in #10075, which will be included in the next release has been included in v5.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants