When voiceover is on, it doesn't seem to read the empty-filter-message properly and is cut off before it is read fully. For example when user types in 'aaa', voiceover will start to read 'no results found' but then when I type another 'a' to make it 'aaaa', voiceover will try to say 'no results found' but will be cut off and read back what was inputted (so 'a').
Thanks a lot for the report! I set a milestone for it. We'll check it before the milestone is released. For now, I think you can change the roles or aria-* of inner HTML element using passthrough(pt) prop.
Describe the bug
When voiceover is on, it doesn't seem to read the empty-filter-message properly and is cut off before it is read fully. For example when user types in 'aaa', voiceover will start to read 'no results found' but then when I type another 'a' to make it 'aaaa', voiceover will try to say 'no results found' but will be cut off and read back what was inputted (so 'a').
Reproducer
https://primevue.org/dropdown/#filter
PrimeVue version
Latest
Vue version
3.x
Language
TypeScript
Build / Runtime
Vue CLI App
Browser(s)
Chrome, Microsoft edge
Steps to reproduce the behavior
With the voiceover on, try typing 'aaa' in to the filter input, and then type in another 'a' to make it 'aaaa.'
Expected behavior
Here is a link to as how we think it should work: https://select2.org/selections
When user types in 'aaa' it should read 'no results found' clearly and even when user types in another 'a', it should read 'no results found' clearly.