AutoComplete - Matches stay highlighted after emptying text

AutoComplete - Matches stay highlighted after emptying text

Posted by: alexei_kostevich on 14 September 2017, 12:11 pm EST

• 

  alexei_kostevich

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 14 September 2017, 12:11 pm EST

  Hello,

  We use Wijmo 5 components and the Angular framework to build a rich-form application.

  We have noticed recently that an AutoComplete contains an issue in highlighting matches.

  Steps to reproduce

  1. Type few letters that have matches
  2. Clear the entered text
  3. Expand an AutoComplete drop-down

  Expected
  
  All records are shown without highlighted matches.

  Actual
  
  All records are shown, but some of them are highlighted based on the previously entered text.

  The issue is reproducible in the Wijmo 5 Explorer: http://demos.wijmo.com/5/angular/explorer/explorer/#/input/autocomplete

  Please, could you take a look at the issue and let us know if there is a possible workaround?

  Thank you in advance,
  
  Alexei

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hello Alexie,
  
  This can be avoided by setting cssMatch to “” in textChanged event. For your reference, please refer to the attached code snippet for the same:

  textChanged:function(s,e){
                      if(s.text.length==0){
                          s.cssMatch="";                       
                      }else{
                          s.cssMatch="wj-autocomplete-match";
                      }
                  }

  Hope it helps!

  Thanks,
  
  Manish Kumar Gupta

• 

  alexei_kostevich

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hello Manish,

  Thank you for looking at this! The provided workaround works perfectly!
  
  We would appreciate to get this issue fixed in Wijmo to avoid possible confusion and workarounds

  Thank you,
  
  Alexei

• 

  manish-gupta1

  • Post Options:
  • Link
    Copy

  Posted 14 September 2017, 12:11 pm EST

  Hi Alexei,
  
  Thank you for let me know that suggested solution worked. We have forwarded this issue to the concerned team for further investigation with tracking id 278848. t will be included in the future releases.

  Thanks,
  
  Manish Kumar Gupta

• 

  manish.gupta

  

  • Post Options:
  • Link
    Copy

  Posted 20 January 2018, 6:51 am EST

  Hi Alexei,
  
  We are sorry for the late reply.
  
  This issue has been verified as fixed with build 5.20173.403.

  ~Manish