Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/static/templates/user_presence_row.handlebars

12 lines
595 B
Handlebars
Raw Normal View History

buddy list: Populate user-fade via templates. When we populate the buddy list or update it for activity, we now have buddy_data set a faded flag that is rendered in the template. This avoids some re-rendering overhead and is on the eventual path to having our widget be more data-oriented (and all rendering happens "behind" the widget). We still do direct DOM updates when the compose state changes or when we get peer subscription events.
2018-04-22 17:46:20 +02:00
<li data-user-id="{{user_id}}" class="user_sidebar_entry {{#if num_unread}} user-with-count {{/if}} narrow-filter user_{{type}} {{#if faded}} user-fade {{/if}}">
Remove unused device-related code in activity list. This speeds up rendering big activity lists. When we are ready to add this back, we should measure the performance impact for large lists.
2017-02-25 19:11:04 +01:00
<span class="selectable_sidebar_block">
Reformat user_presence_row.handlebars to have 4-space indents.
2017-02-25 19:00:02 +01:00
<span class="user-status-indicator"></span>
Remove unused my_fullname HTML class.
2017-02-25 19:25:56 +01:00
<a href="{{href}}"
linter: Enforce 2 space indents on tags spread over multiple lines. We make some specific cases of tags use 2 space indents. The case description: * A tag with opening tag spread over multiple lines and closing tag on the same line as of the closing angle bracket of the opening tag. * A tag with opening tag spread over multiple lines and closing tag not on the same line as of the closing angle bracket of the opening tag. Example: Case 1: Not linted: <button type="button" class="btn btn-primary btn-small">{{t "Yes" }}</button> After linting: <button type="button" class="btn btn-primary btn-small">{{t "Yes" }}</button> Case 2: Before linting: <div class = "foo" id = "bar" role = "whatever"> {{ bla }} </div> After linting: <div class = "foo" id = "bar" role = "whatever"> {{ bla }} </div>
2018-04-05 08:38:46 +02:00
data-user-id="{{user_id}}"
data-name="{{name}}"
title="{{name}} {{type_desc}}">{{name}}</a>
Reformat user_presence_row.handlebars to have 4-space indents.
2017-02-25 19:00:02 +01:00
</span>
<span class="count"><span class="value">{{#if num_unread}}{{num_unread}}{{/if}}</span></span>
<span class="arrow"><i class="icon-vector-chevron-down"></i></span>
Fix performance issues with user presence list in large realms. Whenever a user became active, this triggers an immediate presence update event (to show that user as active). The implementation for that event (running on the browsers of all other users in the realm) would fully rerender the presence list, which can be an expensive operation in a large realm, just to update the status for that one user. This fixes that case to just remove the user from the list and then re-insert it at the appropriate index. [Commit message expanded with more details by Tim Abbott]
2016-01-19 21:03:56 +01:00
</li>