4 grammar corrections
source | link

When I make web application designs, every time I style form or overlay boxes with OK and Cancel buttonbuttons. I think of making them different. But is it a good practice?

Some people recommend primary and secondary buttons, but I dontdon't feel 'cancel' is so important to give it a secondary button status, what. What if the application doesntdoesn't have enough secondary buttons,? I dontdon't want to create and use a secondary button only for 'Cancel'.

When I make web application designs, every time I style form or overlay boxes with OK and Cancel button. I think of making them different. But is it a good practice?

Some people recommend primary and secondary buttons but I dont feel 'cancel' is so important to give it a secondary button status, what if the application doesnt have enough secondary buttons, I dont want to create and use a secondary button only for 'Cancel'.

When I make web application designs, every time I style form or overlay boxes with OK and Cancel buttons. I think of making them different. But is it a good practice?

Some people recommend primary and secondary buttons, but I don't feel 'cancel' is so important to give it a secondary button status. What if the application doesn't have enough secondary buttons? I don't want to create and use a secondary button only for 'Cancel'.

3 updated tags
| link
2 edited tags
| link
    Tweeted twitter.com/#!/StackUX/status/111737095772573696
1
source | link