Skip to content
This repository has been archived by the owner on Mar 5, 2018. It is now read-only.

More obvious button states #464

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

More obvious button states #464

wants to merge 1 commit into from

Conversation

DJMyles
Copy link
Contributor

@DJMyles DJMyles commented Jan 13, 2017

Seeks to address #391

Could potentially expand from here but this is is a good start.

I used a negative offset so as to not affect the overall element size as it could affect surrounding elements if used say inline as part of an input group.

screen shot 2017-01-13 at 12 48 25 pm

Definition of Done

  • Content/documentation reviewed by Julian or someone in the Content Team
  • UX reviewed by Gary or someone the Design team
  • Code reviewed by one of the core developers
  • Acceptance Testing
  • Stakeholder/PO review
  • CHANGELOG updated

@elisechant
Copy link

I think this should be visually approved, not just PR'ed.

@klepas
Copy link
Contributor

klepas commented Jan 13, 2017

@elisechant Yup, I want Gary to be across these.

@AndrewArch
Copy link

can I suggest that on the 'disabled' button, we use the lightest text colour possible that is still 4.5:1 contrast, eg maybe #404040 or lighter

@gazhands
Copy link

Any chance of seeing a live working demo?

@klepas
Copy link
Contributor

klepas commented Jan 16, 2017

@gazhands I’ll deploy one after lunch for you review.

@klepas
Copy link
Contributor

klepas commented Jan 16, 2017

@gazhands
Copy link

Thanks for the work so far everyone. I feel there's some more iteration on the visual design (of the buttons). Balancing all three states needs to be conceded (hover focus, and active) and getting these right, especially on touch screens.

@klepas
Copy link
Contributor

klepas commented Jan 16, 2017

@gazhands Cool.

I feel there's some more iteration on the visual design (of the buttons). Balancing all three states needs to be conceded (hover focus, and active) and getting these right, especially on touch screens.

Could you elaborate? Does this mean we need to give this to the design clinic?

I’m happy to work any design changes into the 2.x work, so knowing what the go is re. buttons soon would be great. (:

@gazhands
Copy link

Don't mind who picks this up but design clinic is a good start. Defo keen to have it for 2.0.

@klepas
Copy link
Contributor

klepas commented Jan 16, 2017

Don't mind who picks this up but design clinic is a good start. Defo keen to have it for 2.0.

*nod*

We will likely look at buttons within the coming two weeks as we write 2.x, so I propose we bring it up tomorrow.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants