pinafore/src/routes/_components/status/Status.html

373 lines
16 KiB
HTML
Raw Normal View History

<article id={elementId}
class={className}
2018-02-19 18:46:30 +00:00
tabindex="0"
aria-posinset={index + 1}
aria-setsize={length}
aria-label={ariaLabel}
on:recalculateHeight
ref:article
>
{#if showHeader}
<StatusHeader {...params} />
{/if}
<StatusAuthorName {...params} />
<StatusAuthorHandle {...params} />
{#if !isStatusInOwnThread}
<StatusRelativeDate {...params} {...timestampParams} />
{/if}
<StatusSidebar {...params} />
{#if spoilerText}
<StatusSpoiler {...params} {spoilerShown} on:recalculateHeight />
{/if}
{#if !showContent}
<StatusMentions {...params} />
{/if}
{#if content && (showContent || preloadHiddenContent)}
<StatusContent {...params} shown={showContent}/>
{/if}
<!-- Apparently it's possible for spoilered content to sometimes have embeds, but I can't figure out how.
Don't bother optimizing this with the preloadHiddenContent. -->
{#if showCard && showContent}
<StatusCard {...params} />
{/if}
{#if showMedia }
<StatusMediaAttachments {...params} on:recalculateHeight />
{/if}
{#if showPoll && (showContent || preloadHiddenContent)}
<StatusPoll {...params} shown={showContent} on:recalculateHeight />
{/if}
{#if isStatusInOwnThread}
<StatusDetails {...params} {...timestampParams} />
{/if}
{#if !isStatusInNotification}
<StatusToolbar {...params} {replyShown} on:recalculateHeight on:focusArticle="focusArticle()" />
{/if}
{#if replyShown}
<StatusComposeBox {...params} on:recalculateHeight />
{/if}
2018-01-11 04:45:02 +00:00
</article>
{#if enableShortcuts}
<Shortcut scope={shortcutScope} key="o" on:pressed="open()" />
<Shortcut scope={shortcutScope} key="p" on:pressed="openAuthorProfile()" />
<Shortcut scope={shortcutScope} key="m" on:pressed="mentionAuthor()" />
feat: Add support for keyboard shortcuts (#870) * Add support for keyboard shortcuts. This change introduces a Shortcut component for defining global keyboard shortcuts from whichever component makes more sense. This change also adds an initial set of navigation shortcuts: - Backspace to leave a modal dialog or to go back - g t to go to the federated timeline - g f to go to the favorite page - g h to go to the home page - g n to go to the notification page - g c to go to the community page - s to go to the search page These shortcuts are loaded asynchronously from _layout.html In modal dialogs, shortcuts are also modal, to avoid strange or overly complex behavior. This is implemented by grouping shortcuts into scopes, and activating a separate 'modal' scope when entering a modal dialog, so a separate set of shortcuts can be enabled in modal dialog. Modal dialogs can be exited by pressing 'Backspace'. * Navigate up/down lists using keyboard shortcuts. This change introduces keyboard shortcuts for navigating in lists and virtual lists. j or arrow up selects the next element, k or arrow down, the previous element. Selecting an element scrolls the list up and down, as necessary. This change also allows directing keyboard shortcuts to the active element and defines the following shortcuts, for the active status: - f to favorite or unfavorite it - b to boost or unboost it - r to reply to it - o to open its thread - x to toggle the display of a CW - y to toggle the display of sensitive medias This works by defining a keyboard shortcut scope for each list element. A new component, ScrollListShortcuts, keeps track of the active element, based on list or virtual list elements and redirects shortcuts to the active element's scope. ScrollListShortcuts keeps the active element in the current realm of the store, so the active element is restored when going back to the list. * Typing h or ? displays the list of available keyboard shortcuts. This change introduces a new modal dialog that documents the list of available shortcuts.
2019-01-13 18:03:29 +00:00
{/if}
2018-01-11 04:45:02 +00:00
<style>
2018-01-16 16:38:23 +00:00
.status-article {
padding: var(--status-pad-v) var(--status-pad-h);
2018-01-11 04:45:02 +00:00
display: grid;
grid-template-areas:
"header header header header"
"sidebar author-name author-handle relative-date"
"sidebar spoiler spoiler spoiler"
"sidebar spoiler-btn spoiler-btn spoiler-btn"
"sidebar mentions mentions mentions"
"sidebar content content content"
"sidebar card card card"
"sidebar media-grp media-grp media-grp"
"sidebar poll poll poll"
"media media media media"
2018-03-30 09:06:17 +01:00
"....... toolbar toolbar toolbar"
"compose compose compose compose";
2018-02-10 06:01:44 +00:00
grid-template-columns: min-content minmax(0, max-content) 1fr min-content;
2018-03-30 09:06:17 +01:00
grid-template-rows: repeat(8, max-content);
}
2018-01-16 16:38:23 +00:00
.status-article.tap-on-status {
cursor: pointer;
}
2018-02-07 04:54:49 +00:00
.status-article.status-in-timeline {
border-bottom: 1px solid var(--main-border);
}
.status-article.status-direct {
background-color: var(--status-direct-background);
}
.status-article.status-in-own-thread {
grid-template-areas:
"sidebar author-name"
"sidebar author-handle"
"spoiler spoiler"
"spoiler-btn spoiler-btn"
"mentions mentions"
"content content"
"card card"
"media-grp media-grp"
"media media"
"poll poll"
"details details"
2018-03-30 09:06:17 +01:00
"toolbar toolbar"
"compose compose";
grid-template-columns: min-content 1fr;
2018-03-30 09:06:17 +01:00
grid-template-rows: repeat(7, max-content);
}
2018-01-11 04:45:02 +00:00
</style>
<script>
2018-02-04 18:50:39 +00:00
import StatusSidebar from './StatusSidebar.html'
import StatusHeader from './StatusHeader.html'
import StatusAuthorName from './StatusAuthorName.html'
import StatusAuthorHandle from './StatusAuthorHandle.html'
import StatusRelativeDate from './StatusRelativeDate.html'
import StatusDetails from './StatusDetails.html'
import StatusCard from './StatusCard.html'
2018-02-04 18:50:39 +00:00
import StatusToolbar from './StatusToolbar.html'
import StatusMediaAttachments from './StatusMediaAttachments.html'
2018-02-04 20:18:22 +00:00
import StatusContent from './StatusContent.html'
import StatusSpoiler from './StatusSpoiler.html'
2018-03-30 09:06:17 +01:00
import StatusComposeBox from './StatusComposeBox.html'
import StatusMentions from './StatusMentions.html'
import StatusPoll from './StatusPoll.html'
feat: Add support for keyboard shortcuts (#870) * Add support for keyboard shortcuts. This change introduces a Shortcut component for defining global keyboard shortcuts from whichever component makes more sense. This change also adds an initial set of navigation shortcuts: - Backspace to leave a modal dialog or to go back - g t to go to the federated timeline - g f to go to the favorite page - g h to go to the home page - g n to go to the notification page - g c to go to the community page - s to go to the search page These shortcuts are loaded asynchronously from _layout.html In modal dialogs, shortcuts are also modal, to avoid strange or overly complex behavior. This is implemented by grouping shortcuts into scopes, and activating a separate 'modal' scope when entering a modal dialog, so a separate set of shortcuts can be enabled in modal dialog. Modal dialogs can be exited by pressing 'Backspace'. * Navigate up/down lists using keyboard shortcuts. This change introduces keyboard shortcuts for navigating in lists and virtual lists. j or arrow up selects the next element, k or arrow down, the previous element. Selecting an element scrolls the list up and down, as necessary. This change also allows directing keyboard shortcuts to the active element and defines the following shortcuts, for the active status: - f to favorite or unfavorite it - b to boost or unboost it - r to reply to it - o to open its thread - x to toggle the display of a CW - y to toggle the display of sensitive medias This works by defining a keyboard shortcut scope for each list element. A new component, ScrollListShortcuts, keeps track of the active element, based on list or virtual list elements and redirects shortcuts to the active element's scope. ScrollListShortcuts keeps the active element in the current realm of the store, so the active element is restored when going back to the list. * Typing h or ? displays the list of available keyboard shortcuts. This change introduces a new modal dialog that documents the list of available shortcuts.
2019-01-13 18:03:29 +00:00
import Shortcut from '../shortcut/Shortcut.html'
import { store } from '../../_store/store.js'
import { goto } from '../../../../__sapper__/client.js'
import { registerClickDelegate } from '../../_utils/delegate.js'
import { classname } from '../../_utils/classname.js'
import { checkDomAncestors } from '../../_utils/checkDomAncestors.js'
import { scheduleIdleTask } from '../../_utils/scheduleIdleTask.js'
import { getAccountAccessibleName } from '../../_a11y/getAccountAccessibleName.js'
import { getAccessibleLabelForStatus } from '../../_a11y/getAccessibleLabelForStatus.js'
import { formatTimeagoDate } from '../../_intl/formatTimeagoDate.js'
import { measureText } from '../../_utils/measureText.js'
import { LONG_POST_LENGTH, LONG_POST_TEXT } from '../../_static/statuses.js'
import { absoluteDateFormatter, dayOnlyAbsoluteDateFormatter } from '../../_utils/formatters.js'
import { composeNewStatusMentioning } from '../../_actions/mention.js'
import { createStatusOrNotificationUuid } from '../../_utils/createStatusOrNotificationUuid.js'
import { addEmojiTooltips } from '../../_utils/addEmojiTooltips.js'
import { tryToFocusElement } from '../../_utils/tryToFocusElement.js'
2018-01-11 04:45:02 +00:00
const INPUT_TAGS = new Set(['a', 'button', 'input', 'textarea', 'label'])
const isUserInputElement = node => INPUT_TAGS.has(node.localName)
const isToolbar = node => node.classList.contains('status-toolbar')
const isStatusArticle = node => node.classList.contains('status-article')
2018-03-30 09:06:17 +01:00
2018-01-11 04:45:02 +00:00
export default {
2018-04-20 05:38:01 +01:00
oncreate () {
2019-08-03 21:49:37 +01:00
const { elementId, isStatusInOwnThread, showContent } = this.get()
const { disableTapOnStatus } = this.store.get()
if (!isStatusInOwnThread && !disableTapOnStatus) {
// the whole <article> is clickable in this case
registerClickDelegate(this, elementId, (e) => this.onClickOrKeydown(e))
}
if (!showContent) {
scheduleIdleTask(() => {
// Perf optimization: lazily load the StatusContent when the user is idle so that
// it's fast when they click the "show more" button
this.set({ preloadHiddenContent: true })
})
}
scheduleIdleTask(() => addEmojiTooltips(this.refs.article))
2018-02-10 19:30:13 +00:00
},
2018-01-11 04:45:02 +00:00
components: {
2018-02-04 18:50:39 +00:00
StatusSidebar,
2018-02-04 18:23:18 +00:00
StatusHeader,
StatusAuthorName,
StatusAuthorHandle,
StatusRelativeDate,
StatusDetails,
2018-02-04 18:50:39 +00:00
StatusToolbar,
StatusMediaAttachments,
2018-02-04 20:18:22 +00:00
StatusContent,
StatusCard,
StatusPoll,
2018-03-30 09:06:17 +01:00
StatusSpoiler,
StatusComposeBox,
feat: Add support for keyboard shortcuts (#870) * Add support for keyboard shortcuts. This change introduces a Shortcut component for defining global keyboard shortcuts from whichever component makes more sense. This change also adds an initial set of navigation shortcuts: - Backspace to leave a modal dialog or to go back - g t to go to the federated timeline - g f to go to the favorite page - g h to go to the home page - g n to go to the notification page - g c to go to the community page - s to go to the search page These shortcuts are loaded asynchronously from _layout.html In modal dialogs, shortcuts are also modal, to avoid strange or overly complex behavior. This is implemented by grouping shortcuts into scopes, and activating a separate 'modal' scope when entering a modal dialog, so a separate set of shortcuts can be enabled in modal dialog. Modal dialogs can be exited by pressing 'Backspace'. * Navigate up/down lists using keyboard shortcuts. This change introduces keyboard shortcuts for navigating in lists and virtual lists. j or arrow up selects the next element, k or arrow down, the previous element. Selecting an element scrolls the list up and down, as necessary. This change also allows directing keyboard shortcuts to the active element and defines the following shortcuts, for the active status: - f to favorite or unfavorite it - b to boost or unboost it - r to reply to it - o to open its thread - x to toggle the display of a CW - y to toggle the display of sensitive medias This works by defining a keyboard shortcut scope for each list element. A new component, ScrollListShortcuts, keeps track of the active element, based on list or virtual list elements and redirects shortcuts to the active element's scope. ScrollListShortcuts keeps the active element in the current realm of the store, so the active element is restored when going back to the list. * Typing h or ? displays the list of available keyboard shortcuts. This change introduces a new modal dialog that documents the list of available shortcuts.
2019-01-13 18:03:29 +00:00
StatusMentions,
Shortcut
2018-01-11 04:45:02 +00:00
},
data: () => ({
2019-08-20 03:08:59 +01:00
notification: undefined,
replyVisibility: undefined,
preloadHiddenContent: false,
enableShortcuts: null
}),
2018-01-24 04:56:07 +00:00
store: () => store,
2018-02-10 19:00:56 +00:00
methods: {
2018-04-20 05:38:01 +01:00
onClickOrKeydown (e) {
2019-08-03 21:49:37 +01:00
const { type, keyCode, target } = e
2018-02-10 19:00:56 +00:00
2019-08-03 21:49:37 +01:00
const isClick = type === 'click'
const isEnter = type === 'keydown' && keyCode === 13
if (!isClick && !isEnter) {
return false
2018-02-10 19:00:56 +00:00
}
if (checkDomAncestors(target, isUserInputElement, isStatusArticle)) {
// this element or any ancestors up to the status-article element is
// a user input element
return false
}
if (checkDomAncestors(target, isToolbar, isStatusArticle)) {
// this element or any of its ancestors is the toolbar
return false
}
feat: Add support for keyboard shortcuts (#870) * Add support for keyboard shortcuts. This change introduces a Shortcut component for defining global keyboard shortcuts from whichever component makes more sense. This change also adds an initial set of navigation shortcuts: - Backspace to leave a modal dialog or to go back - g t to go to the federated timeline - g f to go to the favorite page - g h to go to the home page - g n to go to the notification page - g c to go to the community page - s to go to the search page These shortcuts are loaded asynchronously from _layout.html In modal dialogs, shortcuts are also modal, to avoid strange or overly complex behavior. This is implemented by grouping shortcuts into scopes, and activating a separate 'modal' scope when entering a modal dialog, so a separate set of shortcuts can be enabled in modal dialog. Modal dialogs can be exited by pressing 'Backspace'. * Navigate up/down lists using keyboard shortcuts. This change introduces keyboard shortcuts for navigating in lists and virtual lists. j or arrow up selects the next element, k or arrow down, the previous element. Selecting an element scrolls the list up and down, as necessary. This change also allows directing keyboard shortcuts to the active element and defines the following shortcuts, for the active status: - f to favorite or unfavorite it - b to boost or unboost it - r to reply to it - o to open its thread - x to toggle the display of a CW - y to toggle the display of sensitive medias This works by defining a keyboard shortcut scope for each list element. A new component, ScrollListShortcuts, keeps track of the active element, based on list or virtual list elements and redirects shortcuts to the active element's scope. ScrollListShortcuts keeps the active element in the current realm of the store, so the active element is restored when going back to the list. * Typing h or ? displays the list of available keyboard shortcuts. This change introduces a new modal dialog that documents the list of available shortcuts.
2019-01-13 18:03:29 +00:00
this.open()
return true
feat: Add support for keyboard shortcuts (#870) * Add support for keyboard shortcuts. This change introduces a Shortcut component for defining global keyboard shortcuts from whichever component makes more sense. This change also adds an initial set of navigation shortcuts: - Backspace to leave a modal dialog or to go back - g t to go to the federated timeline - g f to go to the favorite page - g h to go to the home page - g n to go to the notification page - g c to go to the community page - s to go to the search page These shortcuts are loaded asynchronously from _layout.html In modal dialogs, shortcuts are also modal, to avoid strange or overly complex behavior. This is implemented by grouping shortcuts into scopes, and activating a separate 'modal' scope when entering a modal dialog, so a separate set of shortcuts can be enabled in modal dialog. Modal dialogs can be exited by pressing 'Backspace'. * Navigate up/down lists using keyboard shortcuts. This change introduces keyboard shortcuts for navigating in lists and virtual lists. j or arrow up selects the next element, k or arrow down, the previous element. Selecting an element scrolls the list up and down, as necessary. This change also allows directing keyboard shortcuts to the active element and defines the following shortcuts, for the active status: - f to favorite or unfavorite it - b to boost or unboost it - r to reply to it - o to open its thread - x to toggle the display of a CW - y to toggle the display of sensitive medias This works by defining a keyboard shortcut scope for each list element. A new component, ScrollListShortcuts, keeps track of the active element, based on list or virtual list elements and redirects shortcuts to the active element's scope. ScrollListShortcuts keeps the active element in the current realm of the store, so the active element is restored when going back to the list. * Typing h or ? displays the list of available keyboard shortcuts. This change introduces a new modal dialog that documents the list of available shortcuts.
2019-01-13 18:03:29 +00:00
},
open () {
2019-08-03 21:49:37 +01:00
const { originalStatusId } = this.get()
goto(`/statuses/${originalStatusId}`)
},
openAuthorProfile () {
2019-08-03 21:49:37 +01:00
const { accountForShortcut } = this.get()
goto(`/accounts/${accountForShortcut.id}`)
},
async mentionAuthor () {
2019-08-03 21:49:37 +01:00
const { accountForShortcut } = this.get()
await composeNewStatusMentioning(accountForShortcut)
},
focusArticle () {
const { elementId } = this.get()
tryToFocusElement(elementId, /* scroll */ true)
2018-02-10 19:00:56 +00:00
}
},
2018-01-15 03:28:50 +00:00
computed: {
originalStatus: ({ status }) => status.reblog ? status.reblog : status,
originalStatusId: ({ originalStatus }) => originalStatus.id,
statusId: ({ status }) => status.id,
notificationId: ({ notification }) => notification && notification.id,
account: ({ notification, status }) => (
(notification && notification.account) || status.account
),
accountId: ({ account }) => account.id,
originalAccount: ({ originalStatus }) => originalStatus.account,
originalAccountId: ({ originalAccount }) => originalAccount.id,
accountForShortcut: ({ originalAccount, notification }) => notification ? notification.account : originalAccount,
visibility: ({ originalStatus }) => originalStatus.visibility,
plainTextContent: ({ originalStatus }) => originalStatus.plainTextContent || '',
plainTextContentOverLength: ({ plainTextContent }) => (
// measureText() is expensive, so avoid doing it when possible.
// Also measureText() typically only makes text shorter, not longer, so we can measure the raw length
// as a shortcut. (The only case where it makes text longer is with short URLs which get expanded to a longer
// placeholder.) This isn't 100% accurate, but we don't need perfect accuracy here because this is just
// to show a "long post" content warning.
plainTextContent.length > LONG_POST_LENGTH && measureText(plainTextContent) > LONG_POST_LENGTH
),
spoilerText: ({ originalStatus, plainTextContentOverLength }) => (
originalStatus.spoiler_text || (plainTextContentOverLength && LONG_POST_TEXT)
),
2018-06-14 16:42:55 +01:00
inReplyToId: ({ originalStatus }) => originalStatus.in_reply_to_id,
uuid: ({ $currentInstance, timelineType, timelineValue, notificationId, statusId }) => (
createStatusOrNotificationUuid($currentInstance, timelineType, timelineValue, notificationId, statusId)
),
elementId: ({ uuid }) => uuid,
shortcutScope: ({ elementId }) => elementId,
isStatusInOwnThread: ({ timelineType, timelineValue, originalStatusId }) => (
(timelineType === 'status' || timelineType === 'reply') && timelineValue === originalStatusId
),
isStatusInNotification: ({ originalStatusId, notification }) => (
notification && notification.status &&
notification.type !== 'mention' && notification.status.id === originalStatusId
),
spoilerShown: ({ $spoilersShown, uuid, $showAllSpoilers }) => (typeof $spoilersShown[uuid] === 'undefined' ? !!$showAllSpoilers : !!$spoilersShown[uuid]),
replyShown: ({ $repliesShown, uuid }) => !!$repliesShown[uuid],
showCard: ({ originalStatus, isStatusInNotification, showMedia, $hideCards }) => (
!$hideCards &&
!isStatusInNotification &&
!showMedia &&
originalStatus.card &&
originalStatus.card.title
),
showPoll: ({ originalStatus }) => (
originalStatus.poll
),
showMedia: ({ originalStatus, isStatusInNotification }) => (
!isStatusInNotification &&
2018-04-20 05:38:01 +01:00
originalStatus.media_attachments &&
originalStatus.media_attachments.length
),
mediaAttachments: ({ originalStatus }) => (
originalStatus.media_attachments
),
sensitiveShown: ({ $sensitivesShown, uuid }) => !!$sensitivesShown[uuid],
sensitive: ({ originalStatus, $markMediaAsSensitive, $neverMarkMediaAsSensitive }) => (
!$neverMarkMediaAsSensitive && ($markMediaAsSensitive || originalStatus.sensitive)
),
originalAccountEmojis: ({ originalAccount }) => (originalAccount.emojis || []),
originalStatusEmojis: ({ originalStatus }) => (originalStatus.emojis || []),
originalAccountDisplayName: ({ originalAccount }) => (originalAccount.display_name || originalAccount.username),
originalAccountAccessibleName: ({ originalAccount, $omitEmojiInDisplayNames }) => {
return getAccountAccessibleName(originalAccount, $omitEmojiInDisplayNames)
},
createdAtDate: ({ originalStatus }) => originalStatus.created_at,
createdAtDateTS: ({ createdAtDate }) => new Date(createdAtDate).getTime(),
absoluteFormattedDate: ({ createdAtDateTS }) => absoluteDateFormatter().format(createdAtDateTS),
shortInlineFormattedDate: ({ createdAtDateTS, $now, $disableRelativeTimestamps }) => (
$disableRelativeTimestamps
? dayOnlyAbsoluteDateFormatter().format(createdAtDateTS)
: formatTimeagoDate(createdAtDateTS, $now)
),
reblog: ({ status }) => status.reblog,
2019-08-20 03:08:59 +01:00
ariaLabel: ({
originalAccount, account, plainTextContent, shortInlineFormattedDate, spoilerText,
showContent, reblog, notification, visibility, $omitEmojiInDisplayNames, $disableLongAriaLabels,
showMedia, sensitive, sensitiveShown, mediaAttachments, showPoll
2019-08-20 03:08:59 +01:00
}) => (
getAccessibleLabelForStatus(originalAccount, account, plainTextContent,
shortInlineFormattedDate, spoilerText, showContent,
reblog, notification, visibility, $omitEmojiInDisplayNames, $disableLongAriaLabels,
showMedia, sensitive, sensitiveShown, mediaAttachments, showPoll
)
),
showHeader: ({ notification, status, timelineType }) => (
(notification && ['reblog', 'favourite', 'poll', 'status', 'update'].includes(notification.type)) ||
2018-04-20 05:38:01 +01:00
status.reblog ||
timelineType === 'pinned'
),
className: ({ visibility, timelineType, isStatusInOwnThread, $underlineLinks, $disableTapOnStatus }) => (classname(
'status-article',
'shortcut-list-item',
'focus-fix',
timelineType !== 'direct' && visibility === 'direct' && 'status-direct',
timelineType !== 'search' && 'status-in-timeline',
feat: Add support for keyboard shortcuts (#870) * Add support for keyboard shortcuts. This change introduces a Shortcut component for defining global keyboard shortcuts from whichever component makes more sense. This change also adds an initial set of navigation shortcuts: - Backspace to leave a modal dialog or to go back - g t to go to the federated timeline - g f to go to the favorite page - g h to go to the home page - g n to go to the notification page - g c to go to the community page - s to go to the search page These shortcuts are loaded asynchronously from _layout.html In modal dialogs, shortcuts are also modal, to avoid strange or overly complex behavior. This is implemented by grouping shortcuts into scopes, and activating a separate 'modal' scope when entering a modal dialog, so a separate set of shortcuts can be enabled in modal dialog. Modal dialogs can be exited by pressing 'Backspace'. * Navigate up/down lists using keyboard shortcuts. This change introduces keyboard shortcuts for navigating in lists and virtual lists. j or arrow up selects the next element, k or arrow down, the previous element. Selecting an element scrolls the list up and down, as necessary. This change also allows directing keyboard shortcuts to the active element and defines the following shortcuts, for the active status: - f to favorite or unfavorite it - b to boost or unboost it - r to reply to it - o to open its thread - x to toggle the display of a CW - y to toggle the display of sensitive medias This works by defining a keyboard shortcut scope for each list element. A new component, ScrollListShortcuts, keeps track of the active element, based on list or virtual list elements and redirects shortcuts to the active element's scope. ScrollListShortcuts keeps the active element in the current realm of the store, so the active element is restored when going back to the list. * Typing h or ? displays the list of available keyboard shortcuts. This change introduces a new modal dialog that documents the list of available shortcuts.
2019-01-13 18:03:29 +00:00
isStatusInOwnThread && 'status-in-own-thread',
$underlineLinks && 'underline-links',
!$disableTapOnStatus && !isStatusInOwnThread && 'tap-on-status'
)),
content: ({ originalStatus }) => originalStatus.content || '',
showContent: ({ spoilerText, spoilerShown }) => !spoilerText || spoilerShown,
// These timestamp params may change every 10 seconds due to now() polling, so keep them
// separate from the generic `params` list to avoid costly recomputes.
timestampParams: ({ createdAtDate, createdAtDateTS, shortInlineFormattedDate, absoluteFormattedDate }) => ({
createdAtDate,
createdAtDateTS,
shortInlineFormattedDate,
absoluteFormattedDate
}),
// This params list deliberately does *not* include `spoilersShown` or `replyShown`, because these
// change frequently and would therefore cause costly recomputes if included here.
// The main goal here is to avoid typing by passing as many params as possible to child components.
2019-08-20 03:08:59 +01:00
params: ({
notification, notificationId, status, statusId, timelineType,
account, accountId, uuid, isStatusInNotification, isStatusInOwnThread,
originalAccount, originalAccountId, visibility,
replyVisibility, spoilerText, originalStatus, originalStatusId, inReplyToId,
2019-08-20 03:08:59 +01:00
enableShortcuts, shortcutScope, originalStatusEmojis
}) => ({
notification,
notificationId,
status,
statusId,
timelineType,
account,
accountId,
uuid,
isStatusInNotification,
isStatusInOwnThread,
originalAccount,
originalAccountId,
visibility,
replyVisibility,
spoilerText,
originalStatus,
2018-06-14 16:42:55 +01:00
originalStatusId,
inReplyToId,
enableShortcuts,
shortcutScope,
originalStatusEmojis
})
2018-01-11 05:31:33 +00:00
}
2018-01-11 04:45:02 +00:00
}
</script>