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

Buy Anything Button Orders' Order is messed up #12911

Open
nopara73 opened this issue Apr 22, 2024 · 6 comments · May be fixed by #12930
Open

Buy Anything Button Orders' Order is messed up #12911

nopara73 opened this issue Apr 22, 2024 · 6 comments · May be fixed by #12930
Assignees
Milestone

Comments

@nopara73
Copy link
Contributor

The newest orders are being sent to the end of the list, which makes no sense.

image

@MaxHillebrand MaxHillebrand added this to the v2.0.8 milestone Apr 22, 2024
@collins-okafor
Copy link
Contributor

would like to work on this

@nopara73
Copy link
Contributor Author

New clue: it seems like after a restart the order is "correct".

Although I suspect the order would be "more correct" if it'd propagate the newest activity to the top instead of creation time.

@collins-okafor
Copy link
Contributor

New clue: it seems like after a restart the order is "correct".

Although I suspect the order would be "more correct" if it'd propagate the newest activity to the top instead of creation time.

Here's my approach, instead of the latest order being on top which would require scrolling the order list when the list becomes many. it would much is easier if the latest order is close to the new order button, this is easier to see without having to scroll up
image

@collins-okafor collins-okafor linked a pull request Apr 24, 2024 that will close this issue
@nopara73
Copy link
Contributor Author

Doesn't feel right to me. IMO it'd be smarter to better to follow the logic of any email client.

@nopara73
Copy link
Contributor Author

Jakob’s Law: Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know.

https://lawsofux.com/jakobs-law/

@soosr
Copy link
Collaborator

soosr commented Apr 29, 2024

Doesn't feel right to me. IMO it'd be smarter to better to follow the logic of any email client.

cACK. It can be implemented once we have the timestamp if messages. #12429

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

Successfully merging a pull request may close this issue.

4 participants