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

Content Unlocking Button Countdown Timer #2195

Closed
neildaniels opened this issue Jun 10, 2019 · 8 comments
Assignees
Milestone

Comments

@neildaniels
Copy link
Contributor

@neildaniels neildaniels commented Jun 10, 2019

It would be helpful to see a timer when a page becomes unlockable.

Screen Shot 2019-06-10 at 1 45 07 PM

@distantnative

This comment has been minimized.

Copy link
Contributor

@distantnative distantnative commented Jun 11, 2019

Would it be irritating if the timer starts counting down from 2:00 but keeps resetting to 2:00 (since the other user is still editing or editing again)?

@nilshoerrmann

This comment has been minimized.

Copy link
Contributor

@nilshoerrmann nilshoerrmann commented Jun 11, 2019

What about switching from the timer to an ellipsis (…) when the other user continues, similar to how messaging app show activity.

@distantnative

This comment has been minimized.

Copy link
Contributor

@distantnative distantnative commented Jun 11, 2019

@nilshoerrmann We do not have that information - we cannot rely on websockets running on every environment. So the curennt implementation is pulling the API every X seconds and retrieving the information when the lock was set last (locking also sends a ping to the API every x seconds).

So there is no way of actual awareness. Questions is if it would be fine to fake it by showing the ellipsis whenever the timestamp is within the last 10-15 seconds. Opinions?

@nilshoerrmann

This comment has been minimized.

Copy link
Contributor

@nilshoerrmann nilshoerrmann commented Jun 11, 2019

Ah, I thought we could utilize that timestamp in some way to know if there are new changes. I have to admit, I have not studied how this feature works in detail and I was just approaching this from a visual perspective.

Why not show an activity icon like the ellipsis instead of the timer until the unlock button is available. If the ellipsis is animated (pulsing for instance), the user will certainly expect activity that blocks the unlock feature. No need for an exact timer then. What do you think?

@distantnative

This comment has been minimized.

Copy link
Contributor

@distantnative distantnative commented Jun 11, 2019

I like that idea

@neildaniels

This comment has been minimized.

Copy link
Contributor Author

@neildaniels neildaniels commented Jun 11, 2019

Agreed that it would be annoying for the timer to continuously reset to "2:00" all the time. I think some ellipses/icon/indicator would be an adequate stand-in, but would still like to hover and be told how long I have to wait.

Perhaps if it's within 60 seconds of being unlock-able, show the timer then?

I'm just bothered by the current implementation that gives no explanation or indication why the "Unlock" button isn't clickable.

@distantnative

This comment has been minimized.

Copy link
Contributor

@distantnative distantnative commented Jun 11, 2019

Just to emphasize: even if it’s within 60 seconds of being unlockable, it might jump up again if there other user returns.

But maybe we can obscure this by

  • under 30 seconds since last activity: show ellipsis
  • 30-120 seconds since last activity: show countdown (might jump back to ellipsis)
  • more than 120 seconds: allow unlock
@distantnative distantnative transferred this issue from getkirby/ideas Oct 11, 2019
@distantnative distantnative self-assigned this Oct 11, 2019
@distantnative distantnative added this to the 3.3.0 milestone Oct 11, 2019
distantnative added a commit that referenced this issue Oct 11, 2019
distantnative added a commit that referenced this issue Oct 12, 2019
@bastianallgeier

This comment has been minimized.

Copy link
Contributor

@bastianallgeier bastianallgeier commented Oct 14, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 participants
You can’t perform that action at this time.