Uneditable title field

[scot.hacker]

While copy/pasting titles around between multiple photos, I keep ending up in this situation where the Title field becomes uneditable. Clicking in the space where it should be does nothing. If I quit and restart it comes back, but then happens again before long.

Update: I have confirmed that this is still happening in 8.1, but the good news is that I now have clear steps to reproduce:

1. With the Info panel open, select several images
2. Paste the same title into all of them, and hit Enter to apply
3. Keeping the selection, modify the title and hit Enter to re-apply
4. The Title field becomes grayed out and stays that way, even after clicking off the selection. It remains disabled until quitting and restarting Lightroom.

OR:

1. With one image selected, edit the Title and hit Enter to apply
2. Right-arrow to go to the next image, Enter to apply
3. Title field becomes permanently disabled

After more experimentation, it seems like what's causing it is simply the act of hitting Enter! If I change titles and don't hit Enter, the changes are still preserved, but the bug is not triggered. But 40 years experience means my muscle memory is to always hit Enter to apply anything. At least I have a workaround now - don't hit Enter after changing Titles!

See screenshot for example of the disabled Title field. I do a lot of batch-titling, so this is hitting my workflow pretty hard.

Note this bug does not exist before 8.0 - I've been habitually hitting Enter in LR titles for years before this bug appeared.

[awesome_coast3767]

I'm still experiencing this issue in version 8.1.1 on a MacBook Pro.  It's not limited to the Title field; I've also had the same issue with the Caption field.

I think the key to reproducing this issue is typing quickly, especially when mutiple photos are selected.  If I wait a second or two after finishing typing my title/caption, then I don't usually see the issue.  I see the issue more often if I hit Enter immediately after finishing typing.

My workaround is to restart the app each time the issue occurs, but restarting frequently is getting old.

[scot.hacker]

Interesting. Seems like there are so few of us experiencing this, and it's very hard to intentionally reproduce. For what it's worth, I haven't seen it happen for around a month now. Nothing changed about my computer - it just stopped, though it had been happening for months. So weird.