Opened 11 years ago
Closed 6 weeks ago
#28908 closed defect (bug) (worksforme)
Adding a menu custom link during autocompletion does not add the full text in firefox
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0 |
Component: | Menus | Keywords: | |
Focuses: | administration | Cc: |
Description
Tested on Firefox 30.0
In Appearance => Menus, creating a menu and adding custom links does not save the full link text under the condition that you have selected an auto complete value and hit the enter key.
Presumably, the auto complete value should be inserted, then the field should be saved with that value.
Submitting/Saving (via enter key):
This applies to both the link URL and the link name. Didn't add the link URL screenshots to save screen space.
Attachments (1)
Change History (11)
#3
@
11 years ago
Issue seems to be due to a Firefox known bug regarding the timing / order of FF's autocomplete internal workings and the keypress event.
The bug is discussed from the perspective of the browser in BugZilla ticket 286933 at https://bugzilla.mozilla.org/show_bug.cgi?id=286933
@
11 years ago
First pass in an attempt to fix firefox's autocomplete bug affecting adding custom menu links. The patch was based on the answer of the linked StackOverflow question: http://stackoverflow.com/questions/2303955/i-have-a-problem-with-keydown-event-and-autocomplete-in-firebox-on-mac
#4
@
11 years ago
- Keywords has-patch added
I figure that this should be discussed before considering any patches, but the workaround is simple enough to prepare just in case.
It's clear that this issue is still in discussion in BugZilla, and whether to go ahead and add the autocompleted text into the field before user scripts are triggered is only one possible option discussed.
This is an issue that has been in talks for 9 years; I don't think any headway is going to be made on it any time soon.
#8
@
4 months ago
Hey all, I have taken a look at this now 10 years later and it looks like this is still an open ticket on Firefox's end. However I have tested and I was unable to replicate this issue now with the latest version of WordPress and Firefox. As of such does this ticket still need to be open? Can anyone else offer any insight here?
#10
@
6 weeks ago
- Keywords has-patch close reporter-feedback removed
- Resolution set to worksforme
- Status changed from new to closed
Hi all, due to the inability to reproduce, the broken screenshots, and age of this ticket, I'm going to close this to help clean up Trac. Feel free to reopen if this is still an issue.
I think I've seen this in Chrome before too.