Is this a regression?
The previous version in which this bug was not present was
@angular/aria@21
Description
What happens to having Input in ComboboxPopupContainer? This just destroys this pattern completely. Clicking on any element that are not ngOption inside the comboboxPopupContainer just close the comboxPopup container?
Is angular aria will just change it approach completely on every major release or what should we expect here?
Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-starter-welzydb5?file=package.json,src%2Fmain.ts,src%2Fmain.html,src%2Fmain.scss,src%2Findex.html
Expected Behavior
If the pattern is still there please add an example of how it can be achieved. The previous example for this pattern was taken down from the .dev site. This is unprofessional. The library just goes stable and this is no good sign of faith.
Actual Behavior
Search Input inside of popup container should be possible.
Environment
Is this a regression?
The previous version in which this bug was not present was
@angular/aria@21
Description
What happens to having Input in ComboboxPopupContainer? This just destroys this pattern completely. Clicking on any element that are not ngOption inside the comboboxPopupContainer just close the comboxPopup container?
Is angular aria will just change it approach completely on every major release or what should we expect here?
Reproduction
StackBlitz link: https://stackblitz.com/edit/components-issue-starter-welzydb5?file=package.json,src%2Fmain.ts,src%2Fmain.html,src%2Fmain.scss,src%2Findex.html
Expected Behavior
If the pattern is still there please add an example of how it can be achieved. The previous example for this pattern was taken down from the .dev site. This is unprofessional. The library just goes stable and this is no good sign of faith.
Actual Behavior
Search Input inside of popup container should be possible.
Environment