Skip to content
This repository has been archived by the owner on Sep 11, 2024. It is now read-only.

Don't reload the DOM if we can jump straight to the RM #253

Merged
merged 1 commit into from
Mar 30, 2016

Conversation

richvdh
Copy link
Member

@richvdh richvdh commented Mar 30, 2016

Adds a missing 'return' statement which meant that, even if we already had the
relevant event loaded into the DOM, we would rebuild it when the user clicked
on the "(^) Unread messages" bar.

Adds a missing 'return' statement which meant that, even if we already had the
relevant event loaded into the DOM, we would rebuild it when the user clicked
on the "(^) Unread messages" bar.
@ara4n
Copy link
Member

ara4n commented Mar 30, 2016

lgtm. is this fixing a filed bug ooi?

@ara4n ara4n assigned richvdh and unassigned ara4n Mar 30, 2016
@richvdh
Copy link
Member Author

richvdh commented Mar 30, 2016

It might help with the "stuck in 'working around vector#foo'" bug. Or not. It's just obviously wrong.

@richvdh richvdh merged commit ec8fecb into develop Mar 30, 2016
@richvdh richvdh deleted the rav/fix_jump_to_read_marker branch March 30, 2016 23:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants