Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.I'm not sure if this is a Project Issue issue or a Drupal.org issue, but... I'm using FF 3.5 on a Mac, fwiw.
To reproduce:
1. Find some issue. Maybe even this one!
2. In the "Project" autocomplete field on the comment form, start typing in a project name, such as "Deve"
3. Arrow down to select the correct project name (Devel) and hit tab.
4. After the spinner goes for a bit, you get the error "The name you entered (Deve) is not a valid project"
It works fine if I hit "enter" instead of "tab", but that's different to how normal autocomplete fields work elsewhere in Drupal (e.g. the node "Authored by" field).
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 667440-1.project-select-js-tab.patch | 738 bytes | dww |
Comments
Comment #1
dww- This is definitely a project_issue problem -- I can reproduce locally.
- I think there's something unholy going on with all the JS being attached to this poor field from #autocomplete_path + #ahah + project_issue.js
- The project_issue.js is clearly wrong, in that it only thinks enter triggers the "blur" that spins the throbber on enter, not tab. Attached patch fixes that. However, it still does the wrong thing in terms of the bug reported here, so I'm leaving this "needs work".
Sadly, this is pretty out of my league for JS hackery. I know enough to get into trouble, but not really enough to get back out again. Especially when we're talking this interaction of both autocomplete.js and ahah.js. I couldn't find any examples of core of fields that use both. There might be some core bug lurking here, I dunno.
Comment #2
webchickI just hit this again and lost 10 minutes with all the various issue refactoring. :P~ I'll try and somehow find time to test this patch.