[BUG] input with dropdown use clear the selected tag won't remove, and click will click on the text not the element.

[Bangothen]

Hi there!

Thanks for submitting an issue to Protractor.

To help us help you better, please do the following before submitting an issue:

1. Review the questions section of CONTRIBUTING.md.
2. Make sure you are not asking a usage or debugging question. If you are, use StackOverflow, Google Group discussion list, or Gitter to get help.
3. Provide a minimally reduced test case. This makes it much more likely that your bug will be fixed. Protractor has a test Angular application available at http://www.protractortest.org/testapp which you can use for the reproducible test case.
4. Fill in the information that corresponds to your type of issue below.
5. Delete this intro and any unrelated text 😄 (if you do not we'll assume you haven't read these instructions and automatically close the issue.)

Bug report

i have a input element which is :

const filterinput = element(by.id(filterInput))
await browser.wait(EC.presenceOf(filterInput));
await browser.wait(EC.elementToBeClickable(filterInput));
await filterInput.click();

i have a default selction inside input box once the test reach click action, i can see it just click the selected tag inside the input box not the input box element, the expected behaviour should be click the input box instead of the text inside the box right ? the ID "filterInput" is the whole inputbox element is not the text element for sure.
and also i was trying to use await filterInput.clear() before doing the click();
it won't clear() anyting.
after i reset the input default value to empty, the click works.

• Node Version: ``
• Protractor Version: 5.4.0
• Angular Version: ``
• Browser(s): ``
• Operating System and Version ``
• Your protractor configuration file
• A relevant example test
• Output from running the test
• Steps to reproduce the bug
• The URL you are running your tests against (if relevant)

Feature Request

• Reasons for adopting new feature
• Is this a breaking change? (How will this affect existing functionality)