UXD input needed - review Endi's proposal

Working on a solution for this.

I have created an alternative solution as a PDF that can be downloaded here - https://fedorahosted.org/freeipa/wiki/Default%20Dialog%20Selection

Thank you for the design. I have a questions related to keyboard usage:

1) When user is navigating by TAB key, the first selected button should be the one furthest to the left to keep the natural flow, right?

2) When a button other than the default is focused, should the default be highlighted the same way as before? I ask because when user hits enter the action associated with focused button will be applied, instead of the default's button action.

Replying to [comment:5 pvoborni]:

Thank you for the design. I have a questions related to keyboard usage:

1) When user is navigating by TAB key, the first selected button should be the one furthest to the left to keep the natural flow, right?

I would agree that by starting with button furthest left would fit with the natural flow of reading, but it wouldn't be the most efficient way to quickly add multiple users. Based on the fact that being able to hit enter and have the additive action be selected by default is what RFE requests, I would say it is best to have the button furthest to the right highlighted first.

2) When a button other than the default is focused, should the default be highlighted the same way as before? I ask because when user hits enter the action associated with focused button will be applied, instead of the default's button action.

Currently the tool uses the buttons hover state to indicate the highlighted button. I think we should keep the same functionality. If the button uses the color fill it should use the highlight style included with the css specified for that button when it is tabbed over. I tried to keep the css for the highlight subtle, we may have to tweak the highlight colors if it is too subtle.

Move all uncompleted tickets to next month bucket.