fix: (platform) fix of defects related to Search Field

[KevinOkamoto]

Please provide a link to the associated issue.

#3086

Please provide a brief summary of this pull request.

The following issues were addressed:

• Platform Search Field: on button hover has wrong styling
• Platform Search Field: the search input is modifying the results and is also case sensitive when camelcasing is part of the word
• Platform Search Field: when long list of data is present and you search a substring, the result popover does not stick to the search field and instead floats.
• Platform Search Filed: Without entering the letter or character autosuggestion is showing, and entering the space bar auto suggestion is showing
• Platform Search Field: Category is not closing even after selected the category from the keyboard.

Please check whether the PR fulfills the following requirements

• the commit message follows the guideline:
  https://github.com/SAP/fundamental-ngx/blob/master/CONTRIBUTING.md
• all items on the PR Review Checklist are addressed :
  https://github.com/SAP/fundamental-ngx/wiki/PR-Review-Checklist

Documentation checklist:

• Documentation Examples

[netlify]

Deploy preview for fundamental-ngx ready!

Built with commit 9250649

https://deploy-preview-3237--fundamental-ngx.netlify.app

[puru-hk]

Tested this issue it is working fine.

[InnaAtanasova]

Search Field with Categories has the following issue:
type something in the input field -> Input Change Text updates with the value
delete the value using the delete key, not the cleat button -> one letter of the value remains.

See screenshots:

[sKudum]

LGTM

[KevinOkamoto]

@InnaAtanasova I fixed issue with input text not updating on deletion of last character.

[stefanoScalzo]

Should take into account spaces, type in Apple with a space, nothing should be there but both apple and pineapple are there

[stefanoScalzo]

see above

[dimamarksman]

LGTM

[KevinOkamoto]

@stefanoScalzo Is there a use-case for including leading whitespace in a search term? I can maybe see a case for including trailing whitespace in the search term. Most search fields I've used ignore leading white-space.

However, I can see a use case where application requirements may want to have a "starts-with" matching algorithm, but then that will be applied within the user provided data source and not applied within the component.

[stefanoScalzo]

where

The UI5 Example takes into account whitespaces

[KevinOkamoto]

The UI5 Example takes into account whitespaces

@stefanoScalzo The UI5 Example is also has the following defect mentioned in the defect list:

Search Filed: Without entering the letter or character autosuggestion is showing. And entering the space bar auto suggestion is showing. to be fixed(suggestions should appear only if atleast one character is input by the user)

in that if you type in one space character, it is matching all strings with one space in the string.

Isn't it better user experience to trim leading whitespace? In my experience, leading whitespace in the search term is usually done by accident, like when the user cuts-and-pastes a string into the search field.