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

116 lines
3.3 KiB
HTML
Raw Normal View History

Disable animations on modals. This seems to fix the page-scroll issue and is also a little less ostentatious. Fixes https://trac.humbughq.com/ticket/243 (imported from commit 5fdbcc62a251303d134aea46a0755984df125c63)
2012-11-05 16:57:52 +01:00
<div class="modal hide" id="keyboard-shortcuts" tabindex="-1" role="dialog"
Wrap extremely long lines in HTML (imported from commit 4a18013ae001223709d91b7433128f8e75ebf399)
2012-10-25 06:09:28 +02:00
aria-labelledby="keyboard-shortcuts-label" aria-hidden="true">
Add keyboard shortcuts dialog. (imported from commit 1adb18597739dd71f4739dcf0c2da34c82598bd6)
2012-10-24 22:53:19 +02:00
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
<h3 id="keyboard-shortcuts-label">Keyboard shortcuts</h3>
</div>
<div class="modal-body">
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
<table class="hotkeys_table table table-striped table-bordered table-condensed">
<thead>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<th colspan="2">Navigation</th>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
</thead>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">Down or j</td>
<td class="definition">Next message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">Up or k</td>
<td class="definition">Previous message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">/</td>
<td class="definition">Initiate a search</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Support J/K as hotkeys for page_down/page_up (imported from commit f4d092e3a3ccd5fad5e39fb6e6c454fbfeddfa50)
2013-07-17 17:37:27 +02:00
<td class="hotkey">PgUp, K</td>
<td class="definition">Scroll up</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Support J/K as hotkeys for page_down/page_up (imported from commit f4d092e3a3ccd5fad5e39fb6e6c454fbfeddfa50)
2013-07-17 17:37:27 +02:00
<td class="hotkey">PgDn, J, Spacebar</td>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="definition">Scroll down</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">End</td>
<td class="definition">Last message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
</table>
Add keyboard shortcuts dialog. (imported from commit 1adb18597739dd71f4739dcf0c2da34c82598bd6)
2012-10-24 22:53:19 +02:00
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
<table class="hotkeys_table table table-striped table-bordered table-condensed">
<thead>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<th colspan="2">Composing messages</th>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
</thead>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">c</td>
<td class="definition">New stream message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">C</td>
<td class="definition">New private message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">Enter or r</td>
<td class="definition">Respond to message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">R</td>
<td class="definition">Respond to author</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">Tab then Enter</td>
<td class="definition">Send message</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
<tr>
Swap Navigation and Composing tabs of Keyboard Shortcuts. (imported from commit 9e8f878ef68e0fba0ade0b1e275cfede0dd88ec7)
2013-02-26 21:12:35 +01:00
<td class="hotkey">Esc</td>
<td class="definition">Cancel compose</td>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</tr>
</table>
Add keyboard shortcuts dialog. (imported from commit 1adb18597739dd71f4739dcf0c2da34c82598bd6)
2012-10-24 22:53:19 +02:00
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
<table class="hotkeys_table table table-striped table-bordered table-condensed">
<thead>
<tr>
<th colspan="2">Narrowing</th>
</tr>
</thead>
<tr>
<td class="hotkey">s</td>
<td class="definition">Narrow by stream</td>
</tr>
<tr>
<td class="hotkey">S</td>
<td class="definition">Narrow by subject</td>
</tr>
<tr>
<td class="hotkey">v</td>
<td class="definition">Narrow to all private messages</td>
</tr>
<tr>
<td class="hotkey">Esc</td>
<td class="definition">Return to home view</td>
</tr>
</table>
Add keyboard shortcuts dialog. (imported from commit 1adb18597739dd71f4739dcf0c2da34c82598bd6)
2012-10-24 22:53:19 +02:00
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
<table class="hotkeys_table table table-striped table-bordered table-condensed">
<thead>
<tr>
<th colspan="2">Miscellaneous</th>
</tr>
</thead>
<tr>
<td class="hotkey">?</td>
<td class="definition">Open keyboard shortcut help</td>
</tr>
Revised message actions and message info popovers Since f8fbf70c8502 had troubles in FF and people did not like the message-info-on-hover, this commit hopefully will work better. Tables are likely the culprit with using dropdowns in FF, so when we stop having the messagelist be at table, we can switch back to dropdowns which are relatively positioned rather than absolutely on the page. (imported from commit c49a5cd45f3439d089146771e2aa0cee6431125a)
2013-07-11 23:06:58 +02:00
<tr>
<td class="hotkey">i</td>
<td class="definition">Open message actions menu</td>
</tr>
Rearrange keyboard shortcuts dialog so it all fits on one screen. So that it is, in fact, navigable via keyboard shortcut. It's not the most beautiful way to do this; in the ideal world the layout would be more properly responsive and could fill up the screen for you when you have the room for it. The issue is that the version of Bootstrap we're running doesn't easily allow for variable-sized modals, and the hassle of showing and hiding a div manually didn't seem worth it. The pixel sizes are specified manually as well, in a way that isn't particularly responsive, because of a few competing desires: 1) For them to appear side-by-side when wide enough 2) For them to stack when not wide enough 3) The fact that they're awkwardly between a span2 and a span3, so we can't just use the Bootstrap responsive layout stuff Finally, the diff here is best viewed with -w. (I also swapped the order of Narrowing and Navigation, which unfortunately clutters the diff.) (imported from commit 62cfa7959d48ce515562713eb48f9d9b33c8cc16)
2013-01-14 19:44:55 +01:00
</table>
Add keyboard shortcuts dialog. (imported from commit 1adb18597739dd71f4739dcf0c2da34c82598bd6)
2012-10-24 22:53:19 +02:00
</div>
<div class="modal-footer">
<button class="btn btn-primary" data-dismiss="modal" aria-hidden="true">Close</button>
</div>
</div>