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

time-to-read display shows different times for the same text #10817

Closed
2 of 8 tasks
hhirtz opened this issue Mar 25, 2020 · 1 comment
Closed
2 of 8 tasks

time-to-read display shows different times for the same text #10817

hhirtz opened this issue Mar 25, 2020 · 1 comment
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.

Comments

@hhirtz
Copy link

hhirtz commented Mar 25, 2020

  • Gitea version (or commit ref): 1.12.0+dev-33-gc61b90253
  • Git version: N/A: web UI issue
  • Operating system: N/A: web UI issue
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
    • N/A: web UI issue
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No: try.gitea.io doesn't provide time-to-read display
    • Not relevant
  • Log gist: N/A: web UI issue

Description

Gitea show how long reading a comment/issue takes. But the value that is shown changes inconsistently, and the same text can take two different times to read.

Reproduce with:

eeeeeeeeeeeeeeeee

e

eeeeeeeeeeeee
  • enter the text above in a text field for an issue, or a comment on an issue. Time is 4:13.
  • remove the e in the middle. Time is 2:0 (should be shown as 02:00, though it's not the point of this issue)
  • write back the e at the same place. Time is 2:1, different from 4:13.

Screenshots

The three steps respectively:

image
image
image

@hhirtz hhirtz changed the title time-to-read display is buggy time-to-read display shows different times for the same text Mar 25, 2020
@jolheiser
Copy link
Member

That isn't time to read. That's a line:column indicator.

Unfortunately it does seem to have some odd behavior, especially on mobile, but that would be an upstream issue.

Hopefully we come up with a good solution in #10729

@jolheiser jolheiser added dependencies type/question Issue needs no code to be fixed, only a description on how to fix it yourself. and removed dependencies labels Mar 25, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/question Issue needs no code to be fixed, only a description on how to fix it yourself.
Projects
None yet
Development

No branches or pull requests

2 participants