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

18 lines
787 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}}">
right sidebar: Expand sidebar block width for greater click area. Fixes #9797
2018-06-01 23:01:22 +02:00
<div 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>
right-sidebar: Narrow pm/group-pm on clicking unread count badge. Fixes #9797. Clicking on the unread count badge on the right sidebar did not narrow the selected pm/group-pm. This commit moves the count div inside selectable_sidebar_block. Also uses flexbox instead of inline-blocks for user presences selectable_sidebar_block.
2018-06-27 00:08:28 +02:00
<a class="user-presence-link"
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}}"
right-sidebar: Narrow pm/group-pm on clicking unread count badge. Fixes #9797. Clicking on the unread count badge on the right sidebar did not narrow the selected pm/group-pm. This commit moves the count div inside selectable_sidebar_block. Also uses flexbox instead of inline-blocks for user presences selectable_sidebar_block.
2018-06-27 00:08:28 +02:00
title="{{name}} {{type_desc}}">
{{name}}
buddy list: Add marker for which user is yourself. This helps make clear what's going on with the potentially confusing "you" user.
2018-11-28 00:07:01 +01:00
{{#if is_current_user}}
<span class="you-indicator">{{t "(you)" }}</span>
{{/if}}
right-sidebar: Narrow pm/group-pm on clicking unread count badge. Fixes #9797. Clicking on the unread count badge on the right sidebar did not narrow the selected pm/group-pm. This commit moves the count div inside selectable_sidebar_block. Also uses flexbox instead of inline-blocks for user presences selectable_sidebar_block.
2018-06-27 00:08:28 +02:00
</a>
<span class="count"><span class="value">{{#if num_unread}}{{num_unread}}{{/if}}</span></span>
right sidebar: Expand sidebar block width for greater click area. Fixes #9797
2018-06-01 23:01:22 +02:00
</div>
user_presence_row.handlebars: Upgrade to font-awesome 4.7 icon prefixes.
2018-07-03 00:46:49 +02:00
<span class="arrow"><i class="fa fa-chevron-down" aria-hidden="true"></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>