fix strings and cleanup badge style

This commit is contained in:
Sean Yesmunt 2019-07-10 12:08:01 -04:00
parent bee401fd84
commit 339a45f3f1
4 changed files with 24 additions and 12 deletions

View file

@ -39,13 +39,20 @@ export function CommentCreate(props: Props) {
<section> <section>
{commentAck !== true && ( {commentAck !== true && (
<div className="card__content markdown-preview"> <div className="card__content markdown-preview">
<p>A few things to know before participating in the comment alpha:</p> <p>{__('A few things to know before participating in the comment alpha:')}</p>
<ul> <ul>
<li>During the alpha, all comments are sent to a LBRY, Inc. server, not the LBRY network itself.</li>
<li>During the alpha, comments are not decentralized or censorship resistant (but we repeat ourselves).</li>
<li> <li>
When the alpha ends, we will attempt to transition comments, but do not promise to so. Any transition will {__('During the alpha, all comments are sent to a LBRY, Inc. server, not the LBRY network itself.')}
likely involve publishing previous comments under a single archive handle. </li>
<li>
{__(
'During the alpha, comments are not decentralized or censorship resistant (but we repeat ourselves).'
)}
</li>
<li>
{__(
'When the alpha ends, we will attempt to transition comments, but do not promise to do so. Any transition will likely involve publishing previous comments under a single archive handle.'
)}
</li> </li>
</ul> </ul>
<Button button="primary" onClick={handleCommentAck} label={__('Got it!')} /> <Button button="primary" onClick={handleCommentAck} label={__('Got it!')} />

View file

@ -1,5 +1,9 @@
@import '~@lbry/components/sass/badge/_index.scss'; @import '~@lbry/components/sass/badge/_index.scss';
.badge {
vertical-align: middle;
}
.badge--tag { .badge--tag {
@extend .badge; @extend .badge;
background-color: lighten($lbry-teal-5, 55%); background-color: lighten($lbry-teal-5, 55%);

View file

@ -179,12 +179,6 @@
margin-bottom: var(--spacing-small); margin-bottom: var(--spacing-small);
} }
.badge {
bottom: -0.12rem;
position: relative;
margin-left: 0;
}
[data-mode='dark'] & { [data-mode='dark'] & {
background-color: darken($lbry-gray-5, 20%); background-color: darken($lbry-gray-5, 20%);
} }

View file

@ -533,5 +533,12 @@
"Unfollow": "Unfollow", "Unfollow": "Unfollow",
"myChannelName": "myChannelName", "myChannelName": "myChannelName",
"This LBC remains yours. It is a deposit to reserve the name and can be undone at any time.": "This LBC remains yours. It is a deposit to reserve the name and can be undone at any time.", "This LBC remains yours. It is a deposit to reserve the name and can be undone at any time.": "This LBC remains yours. It is a deposit to reserve the name and can be undone at any time.",
"Create channel": "Create channel" "Create channel": "Create channel",
"Uh oh. The flux in our Retro Encabulator must be out of whack. Try refreshing to fix it.": "Uh oh. The flux in our Retro Encabulator must be out of whack. Try refreshing to fix it.",
"If you still have issues, your anti-virus software or firewall may be preventing startup.": "If you still have issues, your anti-virus software or firewall may be preventing startup.",
"Reach out to hello@lbry.com for help, or check out": "Reach out to hello@lbry.com for help, or check out",
"A few things to know before participating in the comment alpha:": "A few things to know before participating in the comment alpha:",
"During the alpha, all comments are sent to a LBRY, Inc. server, not the LBRY network itself.": "During the alpha, all comments are sent to a LBRY, Inc. server, not the LBRY network itself.",
"During the alpha, comments are not decentralized or censorship resistant (but we repeat ourselves).": "During the alpha, comments are not decentralized or censorship resistant (but we repeat ourselves).",
"When the alpha ends, we will attempt to transition comments, but do not promise to do so. Any transition will likely involve publishing previous comments under a single archive handle.": "When the alpha ends, we will attempt to transition comments, but do not promise to do so. Any transition will likely involve publishing previous comments under a single archive handle."
} }