Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/compose.html

138 lines
9.0 KiB
HTML
Raw Normal View History

Switch to fixed sidebar layout and remove bootstrap layout hooks. (imported from commit 060340a2febb7b8df6477a3419e7588a8503e377)
2013-08-13 12:52:26 +02:00
<div id="compose">
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<div id="compose-notifications" class="notifications above-composebox">
Hide more things when you "close" the compose box. This change backs off from the always-open-compose-box paradigm, so that when a user "closes" the compose box, they can no longer type text, attach files, etc., and instead, they have buttons to reopen the compose box. (This change does not affect the feature that when you're in reply mode, the compose box stays open.) (imported from commit 32305d5b35f457a83f126a2265defdd98e885a2b)
2013-06-14 22:02:45 +02:00
</div>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<div id="compose-container">
<div id="compose_controls" class="compose-content new-style">
<div id="nonexistent_stream_reply_error" class="alert-error">
<span class="compose-send-status-close">&times;</span>
<span id="compose-reply-error-msg"></span>
</div>
<div id="compose_buttons">
<span class="new_message_button">
<a class="drafts-link no-style" href="#drafts" title="{{ _('Drafts') }} (d)">
<button type="button" class="button small rounded compose_drafts_button">
<span>{{ _('Drafts') }}</span>
</button>
</a>
<span class="alert-draft pull-left">{{ _('Saved as draft') }}</span>
</span>
<span class="new_message_button">
<button type="button" class="button small rounded compose_stream_button"
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
id="left_bar_compose_stream_button_big"
title="{{ _('New topic') }} (c)">
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<span class="compose_stream_button_label">{{ _('New topic') }}</span>
</button>
</span>
{% if not embedded %}
<span class="new_message_button">
<button type="button" class="button small rounded compose_private_button"
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
id="left_bar_compose_private_button_big"
title="{{ _('New private message') }} (x)">
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<span class="compose_private_button_label">{{ _('New private message') }}</span>
</button>
</span>
{% endif %}
<span class="new_message_button">
<button type="button" class="button small rounded compose_reply_button"
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
id="left_bar_compose_reply_button_big"
title="{{ _('Reply') }} (r)">
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<span class="compose_reply_button_label">{{ _('Reply') }}</span>
</button>
</span>
</div>
</div>
<div class="message_comp compose-content">
<div class="alert" id="compose-send-status">
<span class="compose-send-status-close">&times;</span>
<span id="compose-error-msg"></span>
</div>
<div id="compose_invite_users" class="alert home-error-bar"></div>
<div id="compose-all-everyone" class="alert home-error-bar"></div>
<div id="compose-announce" class="alert home-error-bar"></div>
compose: Add subscribe button to the not subscribed stream error message. Before that, we needed to go the stream settings to subscribe to a particular stream. Fixes #3877.
2018-04-04 19:38:09 +02:00
<div id="compose_not_subscribed" class="alert home-error-bar"></div>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<div id="compose_private_stream_alert" class="alert home-error-bar"></div>
<div id="out-of-view-notification" class="notification-alert"></div>
<div class="composition-area">
<button type="button" class="close" id='compose_close' title="{{ _('Cancel compose') }} (Esc)">&times;</button>
<form id="send_message_form" action="/json/messages" method="post">
{{ csrf_input }}
<table class="compose_table">
<tbody>
<tr class="ztable_layout_row">
<td class="ztable_comp_col1" />
<td class="ztable_comp_col2" />
</tr>
<tr id="stream-message">
<td class="message_header_colorblock message_header_stream left_part">
</td>
<td class="right_part">
<span id="compose-lock-icon">
<i class="icon-vector-lock" title="{{ _('This is an invite-only stream') }}"></i>
</span>
<input type="text" class="recipient_box" name="stream" id="stream"
linter: Make html singleton tags use 2 space indentation.
2018-04-03 10:07:23 +02:00
maxlength="30"
value="" placeholder="{{ _('Stream') }}" autocomplete="off" tabindex="0" aria-label="{{ _('Stream') }}"/>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<i class="icon-vector-narrow icon-vector-small"></i>
<input type="text" class="recipient_box" name="subject" id="subject"
linter: Make html singleton tags use 2 space indentation.
2018-04-03 10:07:23 +02:00
maxlength="60"
value="" placeholder="{{ _('Topic') }}" autocomplete="off" tabindex="0" aria-label="{{ _('Topic') }}"/>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
</td>
</tr>
<tr id="private-message">
compose: Add pills for typing in PM recipients. @brockwhittaker wrote the original prototype for having pills in the recipient box when users compose PMs (either 1:1 or huddle). The prototype was test deloyed on our main realm for several weeks. This commit includes all the original CSS and HTML from the prototype. After some things changed with the codebase after the initial test deployment, I made the following changes: * In prior commits I refactored out a module called `user_pill.js` that implemented some common functions against a more streamlined version of `input_pill.js`, and this commit largely integrates with that. * I made changes in a prior commit to handle Zephyr semantics (emails don't get validated) and tested this commit with zephyr. * I fixed a reload bug by extracting code out to `compose_pm_pill.js` and re-ordering some calls to `initialize`. There are still two flaws related to un-pill-ified text in the input: * We could be more aggressive about trying to pill-ify emails when you blur or tab away. * We only look at the pills when you send the message, instead of complaining about the un-pill-ified text. (Some folks may consider that a feature, but it's probably surprising to others.)
2018-03-06 15:07:55 +01:00
<td class="to_text">
<span>{{ _('To') }}:</span>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
</td>
<td class="right_part">
<div class="pm_recipient">
compose: Add pills for typing in PM recipients. @brockwhittaker wrote the original prototype for having pills in the recipient box when users compose PMs (either 1:1 or huddle). The prototype was test deloyed on our main realm for several weeks. This commit includes all the original CSS and HTML from the prototype. After some things changed with the codebase after the initial test deployment, I made the following changes: * In prior commits I refactored out a module called `user_pill.js` that implemented some common functions against a more streamlined version of `input_pill.js`, and this commit largely integrates with that. * I made changes in a prior commit to handle Zephyr semantics (emails don't get validated) and tested this commit with zephyr. * I fixed a reload bug by extracting code out to `compose_pm_pill.js` and re-ordering some calls to `initialize`. There are still two flaws related to un-pill-ified text in the input: * We could be more aggressive about trying to pill-ify emails when you blur or tab away. * We only look at the pills when you send the message, instead of complaining about the un-pill-ified text. (Some folks may consider that a feature, but it's probably surprising to others.)
2018-03-06 15:07:55 +01:00
<div class="pill-container" data-before="{{ _('You and') }}">
<div class="input" contenteditable="true" id="private_message_recipient" name="recipient"
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-no-recipients-text="{{ _('Add one or more users') }}" data-some-recipients-text="{{ _('Add another user...') }}"></div>
compose: Add pills for typing in PM recipients. @brockwhittaker wrote the original prototype for having pills in the recipient box when users compose PMs (either 1:1 or huddle). The prototype was test deloyed on our main realm for several weeks. This commit includes all the original CSS and HTML from the prototype. After some things changed with the codebase after the initial test deployment, I made the following changes: * In prior commits I refactored out a module called `user_pill.js` that implemented some common functions against a more streamlined version of `input_pill.js`, and this commit largely integrates with that. * I made changes in a prior commit to handle Zephyr semantics (emails don't get validated) and tested this commit with zephyr. * I fixed a reload bug by extracting code out to `compose_pm_pill.js` and re-ordering some calls to `initialize`. There are still two flaws related to un-pill-ified text in the input: * We could be more aggressive about trying to pill-ify emails when you blur or tab away. * We only look at the pills when you send the message, instead of complaining about the un-pill-ified text. (Some folks may consider that a feature, but it's probably surprising to others.)
2018-03-06 15:07:55 +01:00
</div>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
</div>
</td>
</tr>
<tr>
<td class="messagebox" colspan="2">
<textarea class="new_message_textarea" name="content" id='compose-textarea'
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
value="" placeholder="{{ _('Compose your message here') }}" tabindex="0" maxlength="10000" aria-label="{{ _('Compose your message here...') }}"></textarea>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<div class="scrolling_list" id="preview_message_area" style="display:none;">
<div id="markdown_preview_spinner"></div>
<div id="preview_content"></div>
</div>
<div class="drag"></div>
<div id="below-compose-content">
<input type="file" id="file_input" class="notvisible pull-left" multiple />
<a class="message-control-button icon-vector-smile"
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
id="emoji_map" href="#" title="{{ _('Add emoji') }}"></a>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<a class="message-control-button icon-vector-font"
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
title="{{ _('Formatting') }}" data-overlay-trigger="markdown-help"></a>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<a class="message-control-button icon-vector-paper-clip notdisplayed"
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
id="attach_files" href="#" title="{{ _('Attach files') }}"></a>
settings: Add option to control Jitsi video chat integration. Fixes #8922.
2018-04-03 01:46:55 +02:00
{% if jitsi_server_url %}
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<a class="message-control-button fa fa-video-camera"
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
id="video_link" href="#" title="{{ _('Add video call') }}"></a>
settings: Add option to control Jitsi video chat integration. Fixes #8922.
2018-04-03 01:46:55 +02:00
{% endif %}
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<a id="undo_markdown_preview"
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
class="message-control-button icon-vector-edit"
style="display:none;" title="{{ _('Write') }}"></a>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<a id="markdown_preview" class="message-control-button icon-vector-eye-open"
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
title="{{ _('Preview') }}"></a>
compose.html: Clean up to use 4 space indentation.
2018-01-27 18:25:34 +01:00
<a class="drafts-link" href="#drafts" title="{{ _('Drafts') }} (d)">{{ _('Drafts') }}</a>
<span id="sending-indicator"></span>
<div id="send_controls" class="new-style">
<label id="enter-sends-label" class="compose_checkbox_label">
<input type="checkbox" id="enter_sends" />{{ _('Press Enter to send') }}
</label>
<button type="submit" id="compose-send-button" class="button small send_message" tabindex="150" title="{{ _('Send') }} (Ctrl + Enter)">{{ _('Send') }}</button>
</div>
</div>
</td>
</tr>
</tbody>
</table>
</form>
</div>
</div>
Move composebox into its own file. Similarly, here, no code should have changed. (imported from commit 0d739a28b4894dd28acea0a3d9ee503109368425)
2013-02-28 19:41:33 +01:00
</div>
</div>