Skip to content
This repository was archived by the owner on Nov 20, 2025. It is now read-only.
This repository was archived by the owner on Nov 20, 2025. It is now read-only.

User experience and bugs #22

@mrkvon

Description

@mrkvon

created by @agatatalita and moved here from ditup/ditapi#37

User experience:

  • there would be nice to have a white space and a footer on the bottom of the website (for a user to be able to scroll text)
  • (iPad) while logging in the button is not visible at first, there is just text. It can be confusing or look unfinished. The same with other buttons which are inactive at first.
  • There could be a link to sign up or back from the login page.
  • When I am sending a contact request placeholder text is black at the beginning and grey after writing some text
  • wrong link in contact request notification email
  • promise error when accepting contact request
  • promise error when reading (unread) messages
  • default content on empty pages
    • messages
  • unread threads should be displayed bold
  • updating messages to read is still failing: server returns the array of updated messages. not just one. fix model etc.!
  • it is quite no intuitive which tags are shown on tags page and what is happening when you click one of them (are there tags similar to this tag shown or just randomised newest again)
  • there could be a message about tagname requirements, I was adding the tag with a capital letter and it was not possible to add it (and no message was shown - just inactive button)
  • on iPad Safari, while I am moving tag to the proper category (drag & drop), the whole page is moving behind (i remember it was kind of iOS issue)
  • information "no messages" while user doesn't have messages would be less confusing than an empty area, similar could be with contacts
  • when clicking again verification link, empty page is loaded and some todo error in notification (ea721b5)
  • followup: what should happen when user's signup and verification fails?
  • when sending message only with spaces, it will fail on backend, but not be validated on frontend (imperfect validation of messages in frontend)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions