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

Fix tab order on Create Group buttons #393

Merged
merged 2 commits into from
May 7, 2018

Conversation

hubudibu
Copy link
Contributor

since the recent theme updates, tabbing out from the group creation step input fields goes to the back button first, instead of the next button. fixing this (and an input field width) while trying to follow our new css conventions.

}

&.field.is-grouped > .control:not(:last-child) {
margin-left: 0.75rem;
Copy link
Contributor

@sandrina-p sandrina-p May 1, 2018

Choose a reason for hiding this comment

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

I would replace this 0.75rem for the correct variable to avoid hardcoded code. $control-padding-horizontal following Bulma docs.

Besides that cool stuff!

Copy link
Member

Choose a reason for hiding this comment

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

Indeed, as this could turn out to be something that gets adjusted in themes as well.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I actually copied this from the bulma source: https://github.com/jgthms/bulma/blob/master/sass/elements/form.sass#L479 and just switched the direction. so in non-gi-specific grouped fields, that padding will always be 0.75rem and won't be adjusted by any variable.

I agree, It would totally make more sense to use a variable here, but then it wouldn't be consistent with other similar bulma classes.

so, should I still proceed and change this to a var?

<button
class="button is-light is-large"
@click="prev"
:disabled="!this.currentStep"
Copy link
Member

Choose a reason for hiding this comment

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

While we're at it... who is fixing this v-if / :disabled conflict?

Copy link
Contributor

Choose a reason for hiding this comment

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

this is fixed on #390 😄

@hubudibu hubudibu force-pushed the fix/createGroup-theme branch from 3b3e0fd to eeb5ea7 Compare May 7, 2018 13:58
@taoeffect taoeffect merged commit 13533a0 into okTurtles:master May 7, 2018
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.

3 participants