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

Fix handling of holes in threads #1513

Closed
gergely-ujvari opened this Issue Sep 18, 2014 · 7 comments

Comments

Projects
None yet
6 participants
@gergely-ujvari
Contributor

gergely-ujvari commented Sep 18, 2014

This first part has been fixed. See below for bug description.

Currently if you sort by the viewer by Newest and if you have a hole annotation (Saying message not available) then this climbs at the top, because of our sorting alg.

This is not ideal because I want my most recently created annotations to be in top.


EDITED by @tilgovi

The stream also has holes when replies load before parents. We should probably do something smarter here like show the replies and load the parents on click, something like what Twitter is doing.

  • Preserve holes in threads
  • Style the holes and decide what to show
  • Decide how and when to attempt to load more context in the stream moved to #1713
@tilgovi

This comment has been minimized.

Show comment
Hide comment
@tilgovi

tilgovi Sep 23, 2014

Contributor

Changing the title of this to "Holes in threads".

Contributor

tilgovi commented Sep 23, 2014

Changing the title of this to "Holes in threads".

@tilgovi tilgovi changed the title from Message not available vs sorting the viewer by Newest to Design behavior when threads have holes Sep 23, 2014

@tilgovi

This comment has been minimized.

Show comment
Hide comment
@tilgovi

tilgovi Sep 23, 2014

Contributor

"Design behavior when threads have holes" is what I went with.

Contributor

tilgovi commented Sep 23, 2014

"Design behavior when threads have holes" is what I went with.

@tilgovi

This comment has been minimized.

Show comment
Hide comment
@tilgovi

tilgovi Sep 26, 2014

Contributor

Just want to call out my comment in #1525 as particularly relevant for anyone tackling this. #1525 (comment)

Contributor

tilgovi commented Sep 26, 2014

Just want to call out my comment in #1525 as particularly relevant for anyone tackling this. #1525 (comment)

@tilgovi tilgovi added the 1 - Ready label Oct 7, 2014

@tilgovi tilgovi changed the title from Design behavior when threads have holes to As a user, I should see where annotations are unavailable Oct 8, 2014

@tilgovi tilgovi changed the title from As a user, I should see where annotations are unavailable to As a user, I should see when annotations are unavailable in a thread Oct 8, 2014

@tilgovi tilgovi added the Story label Oct 8, 2014

@JakeHartnell

This comment has been minimized.

Show comment
Hide comment
@JakeHartnell

JakeHartnell Oct 30, 2014

Contributor

This bug is even more annoying on the stream, we have 2 annotations that just sit at the top now even though they were made awhile ago:
mozilla_firefox

You can see this live on https://hypothes.is/stream

We should probably tackle this quickly, since deleted "Message Not Available" annotations push down everything else on the stream.

Contributor

JakeHartnell commented Oct 30, 2014

This bug is even more annoying on the stream, we have 2 annotations that just sit at the top now even though they were made awhile ago:
mozilla_firefox

You can see this live on https://hypothes.is/stream

We should probably tackle this quickly, since deleted "Message Not Available" annotations push down everything else on the stream.

@JakeHartnell

This comment has been minimized.

Show comment
Hide comment
@JakeHartnell

JakeHartnell Oct 31, 2014

Contributor

Part of this has been addressed by 5a5368b, annotations are no longer piled on top of the stream.

Contributor

JakeHartnell commented Oct 31, 2014

Part of this has been addressed by 5a5368b, annotations are no longer piled on top of the stream.

@nickstenning nickstenning removed the Story label Nov 4, 2014

@nickstenning nickstenning changed the title from As a user, I should see when annotations are unavailable in a thread to Fix handling of holes in threads Nov 4, 2014

@Treora Treora added 3 - Done and removed 1 - Backlog labels Nov 18, 2014

@JakeHartnell JakeHartnell added 1 - Backlog and removed 3 - Done labels Nov 18, 2014

@aron aron removed the 1 - Backlog label Nov 24, 2014

@aron aron self-assigned this Nov 24, 2014

@aron

This comment has been minimized.

Show comment
Hide comment
@aron

aron Nov 24, 2014

Contributor

Could someone give me an up-to-date summary of this ticket and steps to reproduce the remaining to-dos. Currently I only have the proposed solution to #1525 to go on. /cc @gergely-ujvari

Contributor

aron commented Nov 24, 2014

Could someone give me an up-to-date summary of this ticket and steps to reproduce the remaining to-dos. Currently I only have the proposed solution to #1525 to go on. /cc @gergely-ujvari

@aron

This comment has been minimized.

Show comment
Hide comment
@aron

aron Nov 25, 2014

Contributor

I'm breaking this ticket up, to leave this one just dealing with bugs around holes in the thread across the application.

I've moved the issue of how we deal with conversations in the stream to #1713. This can encompass #1644 and #1712. I think we need to take a more detailed look at the stream what it's supposed to be doing compared to what it's currently doing and go from there.

Contributor

aron commented Nov 25, 2014

I'm breaking this ticket up, to leave this one just dealing with bugs around holes in the thread across the application.

I've moved the issue of how we deal with conversations in the stream to #1713. This can encompass #1644 and #1712. I think we need to take a more detailed look at the stream what it's supposed to be doing compared to what it's currently doing and go from there.

@aron aron added 3 - Done and removed 2 - In Progress labels Dec 2, 2014

@tilgovi tilgovi closed this Dec 4, 2014

@nickstenning nickstenning removed the 3 - Done label Dec 16, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment