Odd issue with cp search forms

Ouverte
  • Quelque chose ne va pas ?
#5,128 1 commentaire 0 réactions 1 personne assignée Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

@Yulyaswan y travaille déjà.

Depuis le 14/2/2026.

Évaluation

Cette issue n'a pas encore été évaluée.

Description

https://github.com/user-attachments/assets/a74a8e35-c968-4003-88f1-b92d72b2b3d5

So this is quirky to replicate- you have to get the timing just right. But if you are typing in a search- members cp is a good place to see this- you type the first 3 letters and it fires off the ajax to start searching. In some cases- depending on timing, you type another letter or two and... it just removes them from the search. Not always- I think it depends on the timing of the ajax firing. But if you get the timing wrong, you type 'rob' and it searches, you type an additional 'i' then you type an additional 'n' and... it just removes the 'n' from the search field and it's just searching for robi.

Hopefully the video illustrates it. I kind of thing it fires the search, you type another letter or two before it responds, and it refills the search field with what it seached on, losing the extra letter(s) you typed in that interval between firing the search and returning the result and the letters it actually searched on.

Which can be annoying if you're doing a lot of searching and not focusing on the search field so much and all of a sudden what you had typed isn't exactly what's there.

Not at all sure how to fix it, though. I see value in what is showing in the field being what it actually searched on. But... that may not be mittigated by the annoyance of what you typed disappearing. Perhaps do a check to match the searched text on what is currently there and if it doesn't match, keep what's there and fire another search.

Hopefully the video comes through.

Langage dominant
PHP
Étoiles
505
Forks
135
Merge moyen
3 j 7 h
PR mergées (30 j)
7

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ExpressionEngine/ExpressionEngine

Toutes les issues de ExpressionEngine/ExpressionEngine

Issues similaires

Plus d'issues PHP

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.