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

Corrections on feature 'seen' #486

Merged
merged 6 commits into from
Dec 6, 2016
Merged

Conversation

averissimo
Copy link
Member

@averissimo averissimo commented Dec 5, 2016

Correction from new feature

Bug: Show only last seen avatar is not working properly once you start to scroll up and history is fetched. Duplicate avatars are shown and sometimes the last one is not shown.

Solution: Show all seen avatars throughout the conversation

Also makes feature more robust, everytime the conversation gets focus it also requests an update on the metadata and updates it, instead of relying on getting it from history

General correction in YakYak

Bug: I've been noticing through my usage of YakYak that sometimes YakYak starts scrolling up alone without input.

I found out why today why while implementing a more predicted way of getting the read_state: We are using duplicate ids in the interface.

The message id is used in message pane, but also in the conversation list on the left. And this id is important as it is used when redrawing the conversation (to refresh it and get back at the same point).

Solution: Message snippet id now has a prefix

@averissimo averissimo changed the title Corrections on feature seen Corrections on feature 'seen' Dec 5, 2016
@averissimo averissimo changed the title Corrections on feature 'seen' [DO NOT MERGE, still testing] Corrections on feature 'seen' Dec 5, 2016
There was a longstanding bug that a conversation would start requesting
  history and scroll up. This was caused because there would be 2
  elements with the same id, the message in the message pane, and the
  message snippet in the conversation list pane. corrected by adding a
  prefix to the message in the list pane, example: "list_<event_id>"

To make sure we have an updated view of the read state, we get
  conversation metadata everytime we set focus on a conversation.
  and only parse the metadata.
@davibe
Copy link
Contributor

davibe commented Dec 5, 2016

awesome

@averissimo
Copy link
Member Author

It's working without problems so far, change in id didn't seem to break anything :)

Message snippet is also updating with conversation

@averissimo averissimo changed the title [DO NOT MERGE, still testing] Corrections on feature 'seen' Corrections on feature 'seen' Dec 6, 2016
@averissimo
Copy link
Member Author

@davibe been using yakyak a lot today since the last commit was pushed and nothing seems broken :)

should be ready to be merged and tested in a pre-release :)

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

Successfully merging this pull request may close these issues.

None yet

2 participants