Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ower search by "escape mode" : need to get only one owner in the list #130

Open
MaelREBOUX opened this issue Jun 11, 2021 · 5 comments
Open

Comments

@MaelREBOUX
Copy link
Member

Since #127 we now have a bizarre UX that we must correct.

I you search with the "escape button method" -> it opens the owner list window. ok no pb.
Then you choose one owner but the dropdown list is anyway filled with all the owners. Where we expect only the choosed owner from the owner "special window".

I hope I'm clear ?

ms2_cadastrapp_bogue_chauvin_mapstore_2

@offtherailz
Copy link
Collaborator

The input box preserves in the drop down all the results from your last "text" search.

As well as you start typing it will show new results. Having the results of your last search looks more a feature to me. 😄 , because it allows to change my choice without having to clear and type again, if I was wrong.

But I understand that it not exactly the same of the old behavior, and that can be confusing.

So the expected behavior (to clarify for development) is that:

  • when you select a result, the dropdown list should contain only results that match with the text contained in the selection.

Correct?

@tdipisa tdipisa assigned dsuren1 and unassigned tdipisa Jun 22, 2021
@tdipisa
Copy link
Collaborator

tdipisa commented Jul 1, 2021

@MaelREBOUX can you please provide your feedback for the above comment?

@MaelREBOUX
Copy link
Member Author

when you select a result, the dropdown list should contain only results that match with the text contained in the selection

Correct !

typing something -> escape -> special owner window -> select ONE owner -> fullfill the dropdown list with THE owner

@catmorales
Copy link

catmorales commented Aug 18, 2022

This issue has been created to follow : #123 (comment)

We have tested this functionnality just right now on portail-test and the behaviour is the same as above (june 2021).
Our versions are :

@catmorales
Copy link

catmorales commented Aug 18, 2022

@tdipisa Searching for the date, I saw that the original issue was created on june 2021.
At this date, we were in VSR phase on cadastrapp. So I think that you must investigate it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants