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

genus and family dropdowns don't allow scrolling through all entities for Plantae parquet #60

Open
tmesaglio opened this issue Sep 16, 2023 · 7 comments

Comments

@tmesaglio
Copy link
Collaborator

tmesaglio commented Sep 16, 2023

  1. Choose Plantae parquet and select Wategora Reserve as the preloaded place
  2. Click in genus bar and start to scroll down
  3. You can't scroll any further than Celtis

For Smiths Lake, you can get down to Dysoxylum before it stops
Fowlers Gap stops at Zaleya
Mount Annan stops at Casuarina
Grants Beach stops at Desmodium
North Head stops at Ceramium

The family lists are also affected for plants:

Wategora - Ricciaceae
Smiths Lake - Zosteraceae
Fowlers - Zygophyllaceae
Mount Annan - Rhacocarpaceae
Grants Beach - Zosteraceae
North Head - Salicaceae

from a very brief check, seems like the other parquets are not affected

@tmesaglio
Copy link
Collaborator Author

bug initially found by Nick Lambert

@tmesaglio
Copy link
Collaborator Author

it is also now clear to me that there are many genera and families missing from the 'middle' of the list, ie not just the ones after the final name that can be scrolled to

random example I found: Sparganium. It's in the ALA, and there are record of it that can be retrieved via the app (see #62), yet it doesn't appear in any of the genus dropdown lists

@tmesaglio
Copy link
Collaborator Author

so in summary, the choose a genus and choose a family dropdown menus are missing many, many valid taxa that should be there; they neither appear in the list by default, and they cannot be retrieved by searching either

@wcornwell
Copy link
Collaborator

wcornwell commented Sep 19, 2023

this is probably the result of a default setting deep in here: https://selectize.dev/docs/usage. the dropdown thing is set up to try to avoid crashing the browser by allowing 1000's of options and i think there are some tricks to limit the choices in that case

@fontikar
Copy link
Collaborator

the genus menu needs to be a reactive too then...I've definitely seen taxa in dropdown that don't exist in buffer

@wcornwell
Copy link
Collaborator

genus menu is reactive but i think the javascript thing "selectize.js" is very afraid of >1000 options, so it aborts displaying everything in certain cases in a confusing way. My guess is that this is to prevent crashing phones. i'll try to read more...

@wcornwell
Copy link
Collaborator

thought about this more, and taxa lists have to be reactive to allow for changing from plants to butterflies, etc.

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

No branches or pull requests

3 participants