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

Version history drop down is poorly formated #3738

Open
rneher opened this issue Feb 24, 2025 · 2 comments
Open

Version history drop down is poorly formated #3738

rneher opened this issue Feb 24, 2025 · 2 comments
Labels
website Tasks related to the web application

Comments

@rneher
Copy link

rneher commented Feb 24, 2025

(Note sure whether this is a duplicate)

We should make this drop down as least as wide to accommodate the accession and the terms

Image

https://pathoplexus.org/seq/PP_0011CQ4.2

@fhennig, could you look into that?

@fhennig
Copy link
Contributor

fhennig commented Feb 24, 2025

I've put it on the list!

Additional context here: https://loculus.slack.com/archives/C05G172HL6L/p1740403366723609

@theosanderson
Copy link
Member

Also, I would prefer not to have the "Revised" on the original, because really what we mean here is "Old version", the revision is version 2. I would maybe only show "Latest version" and have empty string otherwise.

or 'previous version' in light grey, latest version as is without ()

(we can break this out into a new issue later potentially)
We have some complex logic atm that IIRC assigns all old versions as either "Revised" or "Revoked". I've always been against that because IMO the revision/revocation should be associated with the new version. IMO we could do as Richard says above and simply call old versions "Previous version", in gray.

@chaoran-chen chaoran-chen added the website Tasks related to the web application label Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
website Tasks related to the web application
Projects
None yet
Development

No branches or pull requests

4 participants