Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

More css fixes #1608

Merged
merged 4 commits into from Jun 15, 2018
Merged

More css fixes #1608

merged 4 commits into from Jun 15, 2018

Conversation

neb-b
Copy link

@neb-b neb-b commented Jun 15, 2018

Very minor CSS changes, mostly dealing with thumbnail placeholders in different parts of the app.

Also added react-toggle to style the autoplay switch. In the future, we will move all checkboxes over to this but there were some alignment issues so I didn't want to bother with it right now.
#1539
screen shot 2018-06-15 at 4 11 12 pm

@neb-b neb-b mentioned this pull request Jun 15, 2018
@neb-b neb-b force-pushed the css-fixes branch 2 times, most recently from 1e907f0 to 1e18a26 Compare June 15, 2018 19:56
@neb-b neb-b closed this Jun 15, 2018
@neb-b neb-b reopened this Jun 15, 2018
@neb-b neb-b requested a review from kauffj June 15, 2018 20:06
@lbry-bot lbry-bot assigned kauffj and unassigned neb-b Jun 15, 2018
Copy link
Member

@kauffj kauffj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

None of these I would consider blockers.

@@ -68,6 +71,8 @@ export class FormField extends React.PureComponent<Props> {
);
} else if (type === 'textarea') {
input = <textarea type={type} id={name} {...inputProps} />;
} else if (type === 'checkbox' && useToggle) {
input = <Toggle id={name} {...inputProps} />;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are only 11 checkboxes in the entire app. Is it worth making this all of them?

Also, does Toggle maintain the keyboard usability of native inputs? If we're replacing native form inputs with custom ones, I'd prefer they function the same as native inputs for accessibility and keyboard use.

In this case, that'd probably mean that you can still tab to them and that space toggles the value.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was just one checkbox on the settings page that was messed up due to the postfix overlflowing onto a second line. Didn't spend much time on it but yes, all of the checkboxes will use this style (which supports nice usability)

@@ -8,6 +8,7 @@ type Props = {
children: ?React.Node,
icon: ?boolean,
direction: string,
noPadding?: boolean,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a name for this property that would describe the type of tooltip this is rather than the styling of it?

@@ -29,6 +30,7 @@ class ToolTip extends React.PureComponent<Props> {
'tooltip--right': direction === 'right',
'tooltip--bottom': direction === 'bottom',
'tooltip--left': direction === 'left',
'tooltip--no-padding': noPadding
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same for this class as the above comment.

padding-left: $spacing-vertical * 1/3;

.tooltip__body {
margin-top: 5px;
}
}

.tooltip.tooltip--no-padding {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These .tooltip rules can be nested since it's SCSS

@lbry-bot lbry-bot assigned neb-b and unassigned kauffj and neb-b Jun 15, 2018
@neb-b neb-b merged commit a90870e into master Jun 15, 2018
@neb-b neb-b deleted the css-fixes branch September 10, 2018 19:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants